-
Notifications
You must be signed in to change notification settings - Fork 995
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
Support Amazon Linux 2023 (AL2023 previously AL2022) for AWS Node Templates #3382
Comments
Relevant reference awslabs/amazon-eks-ami#824 (comment) |
Thanks @bryantbiggs - so this isn't GA yet. Will hold off on our testing |
https://aws.amazon.com/blogs/aws/amazon-linux-2023-a-cloud-optimized-linux-distribution-with-long-term-support/ rebranded as AL2023 now and released at GA |
I'm very keen to see this available in Karpenter for its updated kernel which should support @snorlaX-sleeps would you mind updating the issue title to |
yes @andrewleech 😉 thanks for the idea |
Any updates on the plans to add AL2023 support? |
We're tracking AL2023 support in the EKS AMI here: awslabs/amazon-eks-ami#1385 |
@cartermckinnon what would be the settings to choose this for the aws node template? do we need to wait until Karpenter supports it? |
As of right now we don't have any plans to backport support to the alpha APIs, support for the AL2023 AMI family with the beta APIs is in the works for the next release: #5604. You can still use AL2023 via the Custom AMI family today though on both the alpha and beta APIs. |
Tell us about your request
AWS recently released the Amazon Linux 2022 image, a direct replacement for AL2 images.
Would it be possible to support AL2022 in the same way Karpenter supports AL2 with default userdata etc?
Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?
We would like to migrate our Kubernetes infrastructure to use AL2022 as it comes with OS upgrades and removes the default Python2.7 installation (as well as having longer term support)
As we use Ansible + Systems Manager for node configuration, we have to do some manual configuration to work around the fact that the Ansible playbook will only work with Python2.7 as it's the default.
Are you currently working around this issue?
Using the
CUSTOM
AMI family type - we are currently only testing the new AMI in a few accounts.Additional Context
Reading the documentation, it seems to suggest that AL2022 does not install containerd by default.
I can understand why this might be a blocker in terms of native Karpenter support, but wanted to open an issue to start the conversation.
Attachments
No response
Community Note
The text was updated successfully, but these errors were encountered: