You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the best practice
Guidance on recommended practices for managing AMI updates. Some ideas for various sections to consider are:
How to use the latest AMI release version in non-rpod environments and a pinned release version in prod environment(s) with EKS managed node group(s) and Karpenter
When pinning a release version, what is the recommended steps when upgrading to a new Kubernetes version for the node
Ensure customers consult the appropriate release notes for the given AMI K8s and release version prior to upgrading (and where to find those)
Agree that we need to include best practices for working with AMIs. Content could likely live in the Data plane section where we already have some material. Could also consider adding the upgrade-related guidance to the Cluster Upgrades section.
Describe the best practice
Guidance on recommended practices for managing AMI updates. Some ideas for various sections to consider are:
Describe alternatives you've considered
Additional context
The text was updated successfully, but these errors were encountered: