Skip to content

Latest commit

 

History

History
150 lines (93 loc) · 4.33 KB

cluster-scaling-install-addon.md

File metadata and controls

150 lines (93 loc) · 4.33 KB
Raw
copyright lastupdated keywords subcollection
years
2014, 2024
2024-01-03
kubernetes, node scaling, ca, autoscaler
containers

{{site.data.keyword.attribute-definition-list}}

Enabling the cluster autoscaler add-on in your cluster

{: #cluster-scaling-install-addon}

You can enable the add-on from the console or the command the line.

Enabling the cluster autoscaler add-on from the console

{: #autoscaler-enable-console} {: ui}

  1. From the {{site.data.keyword.containerlong_notm}} cluster dashboard, select the cluster where you want to enable autoscaling.
  2. On the Overview page, click Add-ons.
  3. On the Add-ons page, locate the Cluster Autoscaler add-on and click Install

Enabling the cluster autoscaler add-on from the CLI

{: #autoscaler-enable-CLI} {: cli}

  1. Enable the cluster-autoscaler add-on by running the following command.

    ibmcloud ks cluster addon enable cluster-autoscaler --cluster <cluster_name>

    {: pre}

    Example output

    Enabling add-on `cluster-autoscaler` for cluster <cluster_name>...
The add-on might take several minutes to deploy and become ready for use.
OK

    {: screen}

  2. Verify that the add-on is installed and Ready.

    ibmcloud ks cluster addon ls --cluster <cluster_name>

    {: pre}

    Example output

    NAME                 Version   Health State   Health Status   
cluster-autoscaler   1.0.1     normal         Addon Ready

    {: screen}

  3. No worker pools are configured for scaling after enabling the add-on. To set up autoscaling on your worker pools, edit the cluster autoscaler configmap.

Updating the cluster autoscaler add-on

{: #cluster-scaling-install-addon-update-addon}

This topic applies only to the cluster autoscaler add-on. {: important}

If you upgrade your cluster to a version that isn't supported by the cluster autoscaler add-on, your apps might experience downtime and your cluster might not scale. {: important}

The cluster autoscaler has two types of updates.

Patch updates : Patch updates are delivered automatically by IBM and don't contain any feature updates or changes in the supported add-on and cluster versions.

Release updates : Release updates contain new features for the cluster autoscaler or changes in the supported add-on or cluster versions. You must manually apply release updates to your cluster autoscaler add-on.

  1. Check the version of the cluster autoscaler add-on that is deployed in your cluster. If an update is available, review the release notes for the latest add-on version.

    ibmcloud ks cluster addon ls --cluster <cluster_name>

    {: pre}

  2. Update the cluster autoscaler add-on.

    ibmcloud ks cluster addon update cluster-autoscaler --version <version-to-update> --cluster <cluster_name>

    {: pre}

  3. Verify the add-on is successfully updated and Ready.

    ibmcloud ks cluster addon ls --cluster <cluster_name>

    {: pre}

Removing the cluster autoscaler add-on from the console

{: #autoscaler-remove-console} {: ui}

Before disabling the add-on, edit the autoscaler ConfigMap to stop scaling your working pools. {: important}

  1. From the {{site.data.keyword.containerlong_notm}} cluster dashboard, select the cluster where you want to enable autoscaling.
  2. On the Overview page, click Add-ons.
  3. On the Add-ons page, locate the Cluster Autoscaler add-on and click Uninstall

Removing the cluster autoscaler add-on from the CLI

{: #autoscaler-remove-cli} {: cli}

Before disabling the add-on, edit the autoscaler ConfigMap to stop scaling your working pools. {: important}

  1. Disable the cluster-autoscaler add-on.

    ibmcloud ks cluster addon disable cluster-autoscaler --cluster <cluster_name>

    {: pre}

  2. Verify that the add-on was removed.

    ibmcloud ks cluster addon ls --cluster <cluster_name>

    {: pre}