chore(eks): add AL2023_ARM_64_NVIDIA AMI type for managed node groups

[amandladev]

Issue: #35571

Reason for this change:

AWS EKS now supports Amazon Linux 2023 with NVIDIA drivers for ARM64 architecture (AL2023_ARM_64_NVIDIA) for managed node groups, but this AMI type is not available in the CDK EKS constructs. Users who want to leverage ARM64-based GPU instances (like Graviton-based GPU instances) with the latest Amazon Linux 2023 optimized for NVIDIA workloads cannot specify this AMI type through CDK, forcing them to use CloudFormation directly or older AMI types.

Description of changes:

Add support for Amazon Linux 2023 with NVIDIA drivers on ARM64 architecture for EKS managed node groups:

• Add AL2023_ARM_64_NVIDIA to NodegroupAmiType enum: New AMI type following the established naming convention
• Include in gpuAmiTypes array: Ensures proper validation logic for GPU instance types
• Add comprehensive JSDoc documentation: Describes the AMI as "Amazon Linux 2023 with NVIDIA drivers (ARM-64)"
• Maintain backward compatibility: No breaking changes to existing functionality
• Follow established patterns: Consistent with existing AMI type implementations

The implementation enables users to specify ARM64 GPU instances with the latest Amazon Linux 2023 optimized for NVIDIA workloads:

new eks.Nodegroup(this, 'GpuNodeGroup', {
  cluster: cluster,
  amiType: eks.NodegroupAmiType.AL2023_ARM_64_NVIDIA,
  instanceTypes: [new ec2.InstanceType('g5g.xlarge')], // ARM64 GPU instance
});

Description of how you validated changes:

• Unit Tests: All existing EKS tests pass without modifications, confirming no regressions

Checklist:

• My code adheres to the CONTRIBUTING GUIDE and DESIGN GUIDELINES

[aws-cdk-automation]

(This review is outdated)

[ozelalisen]

Changed to chore, as this adding new node group version which is more suitable to chore

✅ Updated pull request passes all PRLinter validations. Dismissing previous PRLinter review.

[mergify]

Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork).

[mergify]

Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork).

[mergify]

This pull request has been removed from the queue for the following reason: pull request dequeued.

Pull request #35578 has been dequeued. Mergify failed to merge the pull request. GitHub can't merge the pull request after 15 retries.
Waiting for the branch protection required status checks to be validated.

You can check the last failing draft PR here: #35589.

You should look at the reason for the failure and decide if the pull request needs to be fixed or if you want to requeue it.
If you do update this pull request, it will automatically be requeued once the queue conditions match again.
If you think this was a flaky issue instead, you can requeue the pull request, without updating it, by posting a @mergifyio requeue comment.

[mergify]

Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork).

[ozelalisen]

@Mergifyio update

[mergify]

update

❌ Mergify doesn't have permission to update

Details

For security reasons, Mergify can't update this pull request. Try updating locally.
GitHub response: refusing to allow a GitHub App to create or update workflow .github/workflows/github-merit-badger.yml without workflows permission

[ozelalisen]

@Mergifyio requeue

[mergify]

requeue

✅ The queue state of this pull request has been cleaned. It can be re-embarked automatically

[mergify]

Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork).

[mergify]

This pull request has been removed from the queue for the following reason: pull request dequeued.

Pull request #35578 has been dequeued. Mergify failed to merge the pull request. GitHub can't merge the pull request after 15 retries.
Waiting for the branch protection required status checks to be validated.

You can check the last failing draft PR here: #35595.

You should look at the reason for the failure and decide if the pull request needs to be fixed or if you want to requeue it.
If you do update this pull request, it will automatically be requeued once the queue conditions match again.
If you think this was a flaky issue instead, you can requeue the pull request, without updating it, by posting a @mergifyio requeue comment.

[mergify]

Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork).

[ozelalisen]

@Mergifyio requeue

[mergify]

requeue

✅ The queue state of this pull request has been cleaned. It can be re-embarked automatically

[mergify]

Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork).

[mergify]

This pull request has been removed from the queue for the following reason: pull request manually updated.

The pull request #35578 has been manually updated.

You can check the last failing draft PR here: #35598.

If you want to requeue this pull request, you can post a @mergifyio requeue comment.

Pull request has been modified.

[ozelalisen]

@Mergifyio dequeue

[mergify]

dequeue

☑️ The pull request is not queued

[mergify]

Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork).

[mergify]

Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork).

[mergify]

This pull request has been removed from the queue for the following reason: pull request dequeued.

Pull request #35578 has been dequeued. Mergify failed to merge the pull request. GitHub can't merge the pull request after 15 retries.
Waiting for the branch protection required status checks to be validated.

You can check the last failing draft PR here: #35601.

You should look at the reason for the failure and decide if the pull request needs to be fixed or if you want to requeue it.
If you do update this pull request, it will automatically be requeued once the queue conditions match again.
If you think this was a flaky issue instead, you can requeue the pull request, without updating it, by posting a @mergifyio requeue comment.

[mergify]

Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork).

[ozelalisen]

@Mergifyio refresh

[mergify]

refresh

✅ Pull request refreshed

[mergify]

Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork).

[github-actions]

Comments on closed issues and PRs are hard for our team to see.
If you need help, please open a new issue that references this one.