Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update Bottlerocket image version on nodegroup upgrade #6923

Conversation

TiberiuGC
Copy link
Contributor

Description

With this PR, eksctl upgrade nodegroup command will fetch the latest image version for managed, eksctl created, Bottlerocket nodegroups and, if necessary, update it.

Closes #6766

Checklist

  • Added tests that cover your change (if possible)
  • Added/modified documentation as required (such as the README.md, or the userdocs directory)
  • Manually tested
  • Made sure the title of the PR is a good description that can go into the release notes
  • (Core team) Added labels for change area (e.g. area/nodegroup) and kind (e.g. kind/improvement)

BONUS POINTS checklist: complete for good vibes and maybe prizes?! 🤯

  • Backfilled missing tests for code in same general area 🎉
  • Refactored something and made the world a better place 🌟

@TiberiuGC TiberiuGC added kind/feature New feature or request area/managed-nodegroup EKS Managed Nodegroups bottlerocket labels Aug 7, 2023
Comment on lines -160 to -161
},
"Version": "1.27"
Copy link
Member

Choose a reason for hiding this comment

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

Was this necessary? If yes, i'm curious to hear why

Copy link
Contributor Author

Choose a reason for hiding this comment

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

On nodegroup upgrades, there is a CFN limitation in which if you specify releaseVersion OR kubernetesVersion you can't update any other property, also you can't update both at the same time. Therefore, even if we run something like eksctl upgrade nodegroup --kubernetes-version 1.27, we'll still try to fetch the latest release version, and if one is found, we won't pass kubernetes version to CFN template.

This was previously required when upgrading kubernetes version as we weren't fetching release version for Bottlerocket.

@TiberiuGC TiberiuGC enabled auto-merge (squash) August 9, 2023 10:44
@TiberiuGC TiberiuGC merged commit d07aadd into eksctl-io:main Aug 9, 2023
cPu1 pushed a commit to cPu1/eksctl that referenced this pull request Aug 11, 2023
TiberiuGC added a commit to TiberiuGC/eksctl that referenced this pull request Aug 24, 2023
idanshoham95 pushed a commit to spotinst/weaveworks-eksctl that referenced this pull request Oct 19, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/managed-nodegroup EKS Managed Nodegroups kind/feature New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[Feature] [Upgrade nodegroup] Update Bottlerocket nodes to latest AMI release version
3 participants