Repository navigation
Use the EKS default Kubernetes version when --version is not set - #8905
Merged
Merged
Conversation
DescribeClusterVersions already reports which version EKS treats as the default, but create cluster ignored it and always used the hardcoded api.DefaultVersion. eksctl now takes the default version only from DescribeClusterVersions: api.DefaultVersion is removed and NewClusterConfig no longer seeds metadata.version, so both the flag path and config files without metadata.version resolve to the EKS default. If EKS does not flag a default, create cluster without a version, --version auto and create nodegroup --version=default fail and ask for an explicit version. Other commands that go through NewCtl, such as get cluster, utils describe-cluster-versions, utils describe-addon-versions and the delete cluster --force fallback, keep working. utils migrate-to-pod-identity now looks up the pod identity agent addon for the cluster's version instead of the previously seeded default. The integration tests' -eksctl.version flag now defaults to the EKS default version, resolved without panicking when it cannot be looked up. Signed-off-by: Nathan Clonts <nclonts@amazon.com>
gustavodiaz7722
approved these changes
Oct 14, 2026
naclonts
enabled auto-merge (squash)
October 14, 2026 19:54
sapphirew
approved these changes
Oct 14, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
create clusternow defaults to the version EKS flags as default inDescribeClusterVersions, instead of the hardcodedapi.DefaultVersion(1.34), which is removed. No more PRs like #8645 to bump the default.If EKS flags no default,
create clusterasks for an explicit--version.Tested in us-west-2:
create clusterwith flags and with-f, both without a version, came up on 1.36 (the current EKS default).Checklist
README.md, or theuserdocsdirectory)area/nodegroup) and kind (e.g.kind/improvement)