Skip to content

feat(templates): upgrade eks to 1.35#2497

Draft
zerospiel wants to merge 1 commit intok0rdent:mainfrom
zerospiel:eksbump
Draft

feat(templates): upgrade eks to 1.35#2497
zerospiel wants to merge 1 commit intok0rdent:mainfrom
zerospiel:eksbump

Conversation

@zerospiel
Copy link
Copy Markdown
Collaborator

What this PR does / why we need it:
Introduces the new NodeadmConfigTemplate object usage instead of the outdated EKSConfigTemplate which used to use the obsolete bootstrap.sh.

Sets the default image to the AL2023 which is the EKS default now since k8s 1.33.

Which issue(s) this PR fixes (optional, Fixes #123):
Closes #2468

WARN: Please do not set the PR Ready for review until the new version of the CAPA with the new NodeadmConfigTemplate is landed

@zerospiel
Copy link
Copy Markdown
Collaborator Author

Verified on the latest gcr.io/k8s-staging-cluster-api-aws/cluster-api-aws-controller:main image (bedb7d3aded87acf38a5ad68d352a80b31ee9edf). The node successfully joined the cluster with the NodeadmConfig, effectively making the EKS cluster ready to use.

Copy link
Copy Markdown
Collaborator

@eromanova eromanova left a comment

Choose a reason for hiding this comment

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

LGTM, but need to wait for the new CAPA version.

@zerospiel zerospiel force-pushed the eksbump branch 2 times, most recently from 99c26db to 602f767 Compare March 19, 2026 13:08
Introduces the new NodeadmConfigTemplate object usage instead of the
outdated EKSConfigTemplate which used to use the obsolete bootstrap.sh.

Sets the default image to the AL2023 which is the EKS default now since
k8s 1.33.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: No status

Development

Successfully merging this pull request may close these issues.

Rework EKS ClusterTemplate to support k8s v1.35

2 participants