Service account tokens used in Container Service for Kubernetes (ACK) clusters that run Kubernetes 1.22 and later versions may expire. For more information, see [Product Changes] Solutions for service account token expiration in Kubernetes 1.22 and later. If the version of the cluster-autoscaler component that you use is earlier than 1.3.9, the system cannot automatically reload or renew the service account token. As as result, the existing token may expire. After the service account token expires, cluster-autoscaler cannot function as normal. To avoid this issue, update cluster-autoscaler.
Affected versions
Clusters whose cluster-autoscaler version is earlier than 1.3.9 are affected. This issue is fixed in cluster-autoscaler 1.3.9 or later versions.
For more information about how to view the version of cluster-autoscaler, see View the version of cluster-autoscaler.
Solution
For clusters that have auto scaling enabled and whose cluster-autoscaler version is earlier than 1.3.9, use the following method to update cluster-autoscaler.
Log on to the ACK console. In the left-side navigation pane, click Cluster.
On the Clusters page, find the cluster that you want to manage and click its name. In the left-side pane, choose .
Click Edit on the right side of Node Scaling.
In the Node Scaling Configuration panel, click OK to update cluster-autoscaler to the latest version.
View the version of cluster-autoscaler
Log on to the ACK console. In the left-side navigation pane, click Cluster.
On the Clusters page, find the cluster that you want to manage and click its name. In the left-side pane, choose .
On the Deployments page, set Namespace to kube-system and search for cluster-autoscaler. Check the version of the cluster-autoscaler image. If the image version is earlier than 1.3.9, update cluster-autoscaler.
