In ACK clusters running Kubernetes 1.22 or later, service account tokens may expire. cluster-autoscaler versions earlier than 1.3.9 cannot automatically reload or renew expired tokens, which causes cluster-autoscaler to stop working.
| Detail | Value |
|---|---|
| Affected versions | cluster-autoscaler earlier than 1.3.9 |
| Fixed versions | cluster-autoscaler 1.3.9 and later |
| Impact | cluster-autoscaler stops working after the service account token expires |
| Action required | Update cluster-autoscaler through the ACK console |
For more information about service account token expiration in Kubernetes 1.22 and later, see [Product Changes] Solutions for service account token expiration in Kubernetes 1.22 and later.
Check your cluster-autoscaler version
Before updating, verify whether your cluster is affected.
Log on to the ACK console. In the left-side navigation pane, click Clusters.
On the Clusters page, find the target cluster and click its name. In the left-side pane, choose Workloads > Deployments.
On the Deployments page, set Namespace to kube-system and search for cluster-autoscaler.
Check the image version. If the version is earlier than 1.3.9, update cluster-autoscaler by following the steps in the next section.
Update cluster-autoscaler
For clusters with auto scaling enabled and cluster-autoscaler earlier than 1.3.9, update the component through the ACK console.
Log on to the ACK console. In the left-side navigation pane, click Clusters.
On the Clusters page, find the target cluster and click its name. In the left-side navigation pane, choose Nodes > Node Pools.
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.