(EKS): (missed AMI type BOTTLEROCKET_x86_64_NVIDIA)

[hossein-zamanian]

Describe the bug

BOTTLEROCKET_x86_64_NVIDIA is not included in the AMI type of EKS node groups.

Expected Behavior

Create a node group for the G4DN.Xlarge instance type using the BOTTLEROCKET_x86_64_NVIDIA AMI.

Current Behavior

Deployment failed with this error

The AMI type for your node group. GPU instance types should use the AL2_x86_64_GPU AMI type, which uses the Amazon EKS-optimized Linux AMI with GPU support. Non-GPU instances should use the AL2_x86_64 AMI type, which uses the Amazon EKS-optimized Linux AMI.

Reproduction Steps

        this.cluster.addNodegroupCapacity(this.id + "-GPUNodeGroup", {
            nodegroupName: this.id + "-GPUNodeGroup",
            labels: this.context.cluster.gpuNodeGroupLabels,
            desiredSize: 1,
            maxSize: 3,
            diskSize: 70,
            instanceTypes: [InstanceType.of(InstanceClass.G4DN, InstanceSize.XLARGE)],
            amiType: NodegroupAmiType.BOTTLEROCKET_x86_64_NVIDIA,
            subnets: {
                subnetType: SubnetType.PUBLIC,
                availabilityZones: [this.vpcStack.availabilityZones[0]],
            },
        });

Possible Solution

potential Solution d38677a

Additional Information/Context

The Amazon Linux GPU Nvidia driver version is 470, so I had to switch to BOTTLEROCKET_x86_64_NVIDIA in order to use a specific feature of the Nvidia driver that is only available in newer versions. However, when this was added to our CDK code, I encountered this issue.

CDK CLI Version

2.94.0 (build 987c329)

Framework Version

No response

Node.js Version

20.10.0

OS

Ubuntu

Language

TypeScript

Language Version

No response

Other information

No response

[khushail]

Thanks for reporting this @hossein-zamanian . Since this is missing, I am converting this to feature request and if you are willing to work on it, please feel free to submit a PR. However community contributions are also welcome.

[github-actions]

⚠️COMMENT VISIBILITY WARNING⚠️

Comments on closed issues are hard for our team to see.
If you need more assistance, please either tag a team member or open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.