Skip to content

Update autoscaler image versions and handle 'latest' Kubernetes version in autoscaler configuration#95

Draft
vrutz wants to merge 1 commit into
masterfrom
bug/dss14-sc-303472-plugin-for-eks-clusters-doesn-t-fully-support
Draft

Update autoscaler image versions and handle 'latest' Kubernetes version in autoscaler configuration#95
vrutz wants to merge 1 commit into
masterfrom
bug/dss14-sc-303472-plugin-for-eks-clusters-doesn-t-fully-support

Conversation

@vrutz

@vrutz vrutz commented Jun 25, 2026

Copy link
Copy Markdown
Contributor

No description provided.

@vrutz vrutz self-assigned this Jun 25, 2026
@vrutz vrutz added this to the 15.0.0 milestone Jun 25, 2026
@vrutz vrutz requested a review from a team June 25, 2026 14:56
"1.32": "v1.32.7",
"1.33": "v1.33.4",
"1.34": "v1.34.3",
"1.35": "v1.35.1"

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

According to the doc, the major + minor versions of the autoscaler should always match the major + minor version of kubernetes.
Instead of maintaining this map, can we more dynamically set the autoscaler image version to ${major}.${minor}.0?

It's unclear bc for example, 1.36 is out in GA, but there is no EKS autoscaling image for it (no tags in the repo https://github.com/kubernetes/autoscaler/tags) and the latest from last week (as of June 25th) is 1.35.1

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It is also not recommended to have a mismatch between versions of kubernetes and autoscaler: https://docs.aws.amazon.com/eks/latest/best-practices/cas.html

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant