[Component Update] Cluster-autoscaler update
In Kubernetes 1.22 and later, service account tokens are at risk of expiration. For more information, see [Product Change] Solution for service account token Expiration in Kubernetes 1.22 and Later. If your cluster uses a version of the cluster-autoscaler component earlier than v1.3.9, the system does not automatically reload and update the token. This may cause the token to expire. After the token expires, the cluster-autoscaler component stops working. You must update the component.
Scope
This issue affects clusters that use a version of the cluster-autoscaler component earlier than v1.3.9. Versions v1.3.9 and later include a fix for this issue and do not require an update.
To check the version of the cluster-autoscaler component, see How to check the cluster-autoscaler component version.
Solution
If cluster autoscaling is enabled for your cluster and you are using a cluster-autoscaler component version earlier than v1.3.9, follow these steps to update cluster-autoscaler.
Log on to the ACK console. In the left navigation pane, click Clusters.
On the Clusters page, click the name of your cluster. In the left navigation pane, click .
-
To the right of Configure Auto Scaling, click Edit.
-
In the Configure Auto Scaling dialog box, click OK to update cluster-autoscaler to the latest version.
Checking the cluster-autoscaler component version
Log on to the ACK console. In the left navigation pane, click Clusters.
On the Clusters page, click the name of your cluster. In the left navigation pane, click .
-
On the Deployments page, set Namespace to kube-system and search for cluster-autoscaler. In the list of deployments, find the workload named cluster-autoscaler. The version tag at the end of its container image address, such as
v1.3.8-9946f60-aliyun, is the current version of the cluster-autoscaler component. If the version is earlier than v1.3.9, you must update the component.