fix(eks): support AL2023

[pahud]

Turning this PR in to draft in favor of the earlier submitted one #29505

Will close this PR when #29505 is merged.

--

This PR improves the Amazon EKS with Amazon Linux 2023 support that allows the cluster to addNodegroupCapacity() correctly.

To make sure it works with the latest KubernetesVersion 1.29 with Amazon EKS, this PR added a new integration test for for that.

Issue # (if applicable)

Closes #29546

Reason for this change

Description of changes

Description of how you validated changes

class EksClusterStack extends Stack {

  private cluster: eks.Cluster;
  private vpc: ec2.IVpc;

  constructor(scope: App, id: string, props?: StackProps) {
    super(scope, id, props);

    // allow all account users to assume this role in order to admin the cluster
    const mastersRole = new iam.Role(this, 'AdminRole', {
      assumedBy: new iam.AccountRootPrincipal(),
    });

    // just need one nat gateway to simplify the test
    // this.vpc = new ec2.Vpc(this, 'Vpc', { natGateways: 1, restrictDefaultSecurityGroup: false });
    this.vpc = ec2.Vpc.fromLookup(this, 'Vpc', { isDefault: true });

    // create the cluster with a default nodegroup capacity
    this.cluster = new eks.Cluster(this, 'Cluster', {
      vpc: this.vpc,
      mastersRole,
      defaultCapacity: 0,
      ...getClusterVersionConfig(this, eks.KubernetesVersion.V1_29),
    });

    this.cluster.addNodegroupCapacity('NG1', {
      amiType: NodegroupAmiType.AL2023_X86_64_STANDARD,
    });
    this.cluster.addNodegroupCapacity('NG2', {
      amiType: NodegroupAmiType.AL2023_ARM_64_STANDARD,
    });
  }
}

kubectl get no
NAME                           STATUS   ROLES    AGE    VERSION
ip-172-31-1-162.ec2.internal   Ready    <none>   118m   v1.29.0-eks-5e0fdde
ip-172-31-2-177.ec2.internal   Ready    <none>   118m   v1.29.0-eks-5e0fdde
ip-172-31-2-211.ec2.internal   Ready    <none>   118m   v1.29.0-eks-5e0fdde
ip-172-31-3-51.ec2.internal    Ready    <none>   118m   v1.29.0-eks-5e0fdde

List nodes and print architecture, osImage and kubeletVersion only:

kubectl get no --no-headers -o custom-columns=NAME:.metadata.name | while read x; do kubectl get no $x -o jsonpath="{.status.nodeInfo}" | jq -r '{ architecture, osImage, kubeletVersion }'; done
{
  "architecture": "arm64",
  "osImage": "Amazon Linux 2023.3.20240304",
  "kubeletVersion": "v1.29.0-eks-5e0fdde"
}
{
  "architecture": "arm64",
  "osImage": "Amazon Linux 2023.3.20240304",
  "kubeletVersion": "v1.29.0-eks-5e0fdde"
}
{
  "architecture": "amd64",
  "osImage": "Amazon Linux 2023.3.20240304",
  "kubeletVersion": "v1.29.0-eks-5e0fdde"
}
{
  "architecture": "amd64",
  "osImage": "Amazon Linux 2023.3.20240304",
  "kubeletVersion": "v1.29.0-eks-5e0fdde"
}

Checklist

• My code adheres to the CONTRIBUTING GUIDE and DESIGN GUIDELINES

---

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license

[aws-cdk-automation]

The pull request linter has failed. See the aws-cdk-automation comment below for failure reasons. If you believe this pull request should receive an exemption, please comment and provide a justification.

A comment requesting an exemption should contain the text Exemption Request. Additionally, if clarification is needed add Clarification Request to a comment.

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

[aws-cdk-automation]

AWS CodeBuild CI Report

• CodeBuild project: AutoBuildv2Project1C6BFA3F-wQm2hXv2jqQv
• Commit ID: 723ec56
• Result: SUCCEEDED
• Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

[guessi]

fyi, I did the same fixed #29505 last week, would you mind look into it ?

[pahud]

@guessi oh I didn't notice you have submitted a PR for that last week. I will turn my PR into Draft in favor of yours.

[pahud]

closed in favor of #29505