Skip to content

Upgrade cluster-autoscaler v1.26.4 -> v1.34.5 - #1073

Merged
arielr-lt merged 1 commit into
masterfrom
chore/upgrade-cluster-autoscaler-1.34
Sep 3, 2026
Merged

arielr-lt merged 1 commit into
masterfrom
chore/upgrade-cluster-autoscaler-1.34

Conversation

@arielr-lt

@arielr-lt arielr-lt commented Sep 3, 2026 •

Copy link
Copy Markdown
Collaborator

Summary

Upgrades cluster-autoscaler on ce-registry-eks from v1.26.4 → v1.34.5 to match the cluster's Kubernetes 1.34 version.

Why

CA was 8 minor versions behind the cluster. Cluster-autoscaler must track the cluster's minor version — its scheduler-simulation code is pinned per release, so a large mismatch causes subtle/broken scale decisions and is unsupported.

Changes

  • Image: cluster-autoscaler:v1.26.4 → v1.34.5 (latest 1.34 patch).
  • ClusterRole storage.k8s.io rule: add volumeattachments (required by v1.34; the v1.26 role lacked it). All other args/IRSA/auto-discovery unchanged.

The cluster runs Kubernetes 1.34 but cluster-autoscaler was pinned at v1.26.4
(8 minor versions behind), which is unsupported — CA's scheduler-simulation
libraries must match the cluster minor version. Bump to v1.34.5 (latest patch
for 1.34).

Also add 'volumeattachments' to the storage.k8s.io ClusterRole rule — the one
permission v1.34 needs that the v1.26 role lacked.

Non-disruptive: CA is control-plane (rolling restart doesn't touch workloads),
and all node groups are currently at desired==min so there is nothing to scale
down. Verified v1.34.5 comes up healthy (leader elected, informers synced, no
RBAC/forbidden errors).
@arielr-lt arielr-lt changed the title chore(eks): upgrade cluster-autoscaler v1.26.4 -> v1.34.5 Upgrade cluster-autoscaler v1.26.4 -> v1.34.5 Sep 3, 2026
@arielr-lt
arielr-lt merged commit 30badee into master Sep 3, 2026
12 checks passed
@arielr-lt
arielr-lt deleted the chore/upgrade-cluster-autoscaler-1.34 branch September 3, 2026 14:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants