-
Notifications
You must be signed in to change notification settings - Fork 4k
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
(aws-eks): Support bottlerocket arm64
AMI's
#14466
Comments
Looks like we are always assuming
@pahud You have some insight on this? Can we use |
Just wanted to ask about the same thing, but for the ECS variant of the image:
An AMI does exist for |
According to the bottlerocket github repo, we do have aws ssm get-parameters --names /aws/service/bottlerocket/aws-k8s-1.20/arm64/latest/image_id
{
"Parameters": [
{
"Name": "/aws/service/bottlerocket/aws-k8s-1.20/arm64/latest/image_id",
"Type": "String",
"Value": "ami-0212d00ded9cb67f4",
"Version": 2,
"LastModifiedDate": "2021-05-20T01:14:42.129000+08:00",
"ARN": "arn:aws:ssm:ap-northeast-1::parameter/aws/service/bottlerocket/aws-k8s-1.20/arm64/latest/image_id",
"DataType": "text"
}
],
"InvalidParameters": []
} I support the PR for it. |
@pahud Thanks. Converting this to a feature request. Happy to accept a contribution here. |
arm64
AMI's
Add support for Bottlerocket AMIs on ARM64 architecture, including AWS Graviton2 instances. Closes #14466 ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
|
Add support for Bottlerocket AMIs on ARM64 architecture, including AWS Graviton2 instances. Closes aws#14466 ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
Add support for Bottlerocket AMIs on ARM64 architecture, including AWS Graviton2 instances. Closes aws#14466 ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
Add support for Bottlerocket AMIs on ARM64 architecture, including AWS Graviton2 instances. Closes aws#14466 ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
We currently only use
x86_64
for bottlerocket AMI's even though sometimesarm64
is needed (for graviton instance types for example).Originaly reported as
EKS: using add_auto_scaling_group_capacity fails OS BOTTLEROCKET and Graviton Instance type
description of the bug:
EKS: using add_auto_scaling_group_capacity fails with machine_image_type=eks.MachineImageType.BOTTLEROCKET and Graviton Instance type
Reproduction Steps
setup an EKS cluster with CDK and then add to it an addition capacity, with BOTTLEROCKET and graviton instance using this:
cdk --version
1.101.0 (build 149f0fc)
The Autoscaling throws and error:
Launching a new EC2 instance. Status Reason: The architecture 'arm64' of the specified instance type does not match the architecture 'x86_64' of the specified AMI. Specify an instance type and an AMI that have matching architectures, and try again. You can use 'describe-instance-types' or 'describe-images' to discover the architecture of the instance type or AMI. Launching EC2 instance failed
What did you expect to happen?
I would expect an AutoScaling group to be created with 2 instances on t4g.large.
What actually happened?
Launching a new EC2 instance. Status Reason: The architecture 'arm64' of the specified instance type does not match the architecture 'x86_64' of the specified AMI. Specify an instance type and an AMI that have matching architectures, and try again. You can use 'describe-instance-types' or 'describe-images' to discover the architecture of the instance type or AMI. Launching EC2 instance failed
Environment
Other
This code swapping out the instance works as expected:
So it appears that CDK is not making the correct AMI decision with Bottlerocket and ARM instance types. However is for intel instance types.
This is 🐛 Bug Report
The text was updated successfully, but these errors were encountered: