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

Bottlerocket bare metal images for EKS Anywhere #7754

Open
csplinter opened this issue Feb 29, 2024 · 0 comments
Open

Bottlerocket bare metal images for EKS Anywhere #7754

csplinter opened this issue Feb 29, 2024 · 0 comments

Comments

@csplinter
Copy link
Member

When EKS Anywhere launched bare metal support in 2022, Bottlerocket was included as the default operating system for nodes in EKS Anywhere clusters to enable a streamlined getting started experience. Since, we have learned that most EKS Anywhere customers running on bare metal have unique hardware and networking configurations that require OS-level customizations and driver support. Bottlerocket's image-based architecture and constrained surface area do not align with these bare metal use cases, and most EKS Anywhere customers running on bare metal have chosen to use Ubuntu or RHEL as the operating system for nodes in their EKS Anywhere clusters.

Starting with the v0.19 EKS Anywhere release, we are deprecating Bottlerocket support for bare metal and it will no longer be the default operating system for EKS Anywhere on bare metal. The EKS Anywhere v0.19 release does not include Bottlerocket bare metal images for Kubernetes version v1.29. Bottlerocket bare metal images for the older Kubernetes versions supported by EKS Anywhere (v1.25 - v1.28) will continue to be maintained and patched until the Kubernetes version reaches end of support in EKS Anywhere. We recommend that you consider Ubuntu or RHEL for EKS Anywhere on bare metal as alternatives. For more information, reference the EKS Anywhere documentation.

Bottlerocket support for EKS Anywhere on vSphere are unaffected by this change.

If you have feedback on this change, please respond to this issue.

@abhay-krishna abhay-krishna pinned this issue Feb 29, 2024
@jiayiwang7 jiayiwang7 unpinned this issue Mar 4, 2024
@abhay-krishna abhay-krishna pinned this issue Mar 4, 2024
@abhay-krishna abhay-krishna unpinned this issue Apr 17, 2024
@abhay-krishna abhay-krishna pinned this issue Apr 17, 2024
@mitalipaygude mitalipaygude unpinned this issue May 2, 2024
@mitalipaygude mitalipaygude pinned this issue May 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant