Open markusl opened 1 day ago
Yes
If props.amiType is not specified, the first element of possibleAmiTypes
would be picked, which is AL2_X86_64.
We'll have to shift the order here and this would cause breaking changes and requires a feature flag.
We welcome community PRs.
@pahud Yes, I noticed amiType
for addNodegroupCapacity
. However, the defaultCapacity
and defaultCapacityInstance
properties of eks.Cluster
do not seem to make it possible to specify AL2023 / Bottlerocket. Is there a workaround for that?
Describe the bug
EKS: EKS uses AL2_x86_64 AmiType in AWS::EKS::Nodegroup instead of AL2023_x86_64_STANDARD
Regression Issue
Last Known Working CDK Version
No response
Expected Behavior
I would expect the latest AMI to be used instead of the old one. Once a cluster is deployed, a message is shown in AWS console: "New AMI release version is available for this node group."
Terraform module also suggests that "Starting on 1.30, AL2023 is the default AMI type for EKS managed node groups" https://registry.terraform.io/modules/terraform-aws-modules/eks/aws/20.29.0
Current Behavior
The following template is generated:
Reproduction Steps
Possible Solution
No response
Additional Information/Context
No response
CDK CLI Version
2.167.1 (build d681b12)
Framework Version
No response
Node.js Version
20
OS
Mac
Language
TypeScript
Language Version
No response
Other information
No response