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

Recommended practice(s) for AMI updates #547

Open
bryantbiggs opened this issue Jul 15, 2024 · 2 comments
Open

Recommended practice(s) for AMI updates #547

bryantbiggs opened this issue Jul 15, 2024 · 2 comments
Assignees
Labels
idea New best practices idea

Comments

@bryantbiggs
Copy link
Member

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)

Describe alternatives you've considered

  • None

Additional context

@bryantbiggs bryantbiggs added the idea New best practices idea label Jul 15, 2024
@svennam92
Copy link
Collaborator

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.

@svennam92 svennam92 assigned svennam92 and unassigned jicowan Aug 12, 2024
@mmerkes
Copy link
Contributor

mmerkes commented Sep 12, 2024

I will work with my team to help craft some guidance here.

@svennam92 svennam92 assigned mmerkes and unassigned svennam92 Sep 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
idea New best practices idea
Projects
None yet
Development

No branches or pull requests

4 participants