✨ Add support for EKSConfig LaunchTemplate bootstrapping for AL2023 using nodeadm

[AmitSahastra]

Description

This PR adds support for using launch template EKSConfig bootstrapping for Amazon Linux 2023 nodes. The EKSConfig controller now able to create bootstrap datasecrete with nodeConfig that will enable using AL2023 images with LaunchTemplates.

⚠️ Prior to this change, CAPA always generated cloud-init-style userData, which is incompatible with AL2023. This patch enables EKS-managed bootstrap using nodeadm via MIME-compliant NodeConfig.

Changes

• Modified EKSConfig controller to fetch AMI ID from AWSManagedMachinePool's launch template
• Added proper condition handling for control plane readiness
• Ensured proper reconciliation when dependencies (AWSManagedControlPlane and AWSManagedMachinePool) become ready

Testing

• Verified EKSConfig correctly generates a bootstrap data secret using a NodeConfig MIME payload when nodeType: al2023 is specified
• Confirmed that node labels are properly set with the AMI ID
• Tested reconciliation behaviour when dependencies are not ready
• Validated that the controller proceeds with data secret creation once dependencies are ready
• Example node output:

k get nodes -o wide
NAME                                          STATUS   ROLES    AGE   VERSION                INTERNAL-IP    EXTERNAL-IP   OS-IMAGE                       KERNEL-VERSION                    CONTAINER-RUNTIME
ip-10-0-183-158.ap-south-1.compute.internal   Ready    <none>   17h   v1.30.11-eks-473151a   10.0.183.158   <none>        Amazon Linux 2023.7.20250527   6.1.134-152.225.amzn2023.x86_64   containerd://1.7.27
ip-10-0-65-54.ap-south-1.compute.internal     Ready    <none>   17h   v1.30.11-eks-473151a   10.0.65.54     <none>        Amazon Linux 2023.7.20250527   6.1.134-152.225.amzn2023.x86_64   containerd://1.7.27

• EKSConfig with nodeType:

apiVersion: bootstrap.cluster.x-k8s.io/v1beta2
kind: EKSConfig
metadata:
  annotations:
    kubectl.kubernetes.io/last-applied-configuration: |
      {"apiVersion":"bootstrap.cluster.x-k8s.io/v1beta2","kind":"EKSConfig","metadata":{"annotations":{},"name":"am-clusterctl-eks-2-pool-0-bootstrap","namespace":"default"},"spec":{"nodeType":"al2023"}}
  creationTimestamp: "2025-06-16T12:26:26Z"
  generation: 1
  labels:
    cluster.x-k8s.io/cluster-name: am-clusterctl-eks-2
  name: am-clusterctl-eks-2-pool-0-bootstrap
  namespace: default
  ownerReferences:
  - apiVersion: cluster.x-k8s.io/v1beta1
    blockOwnerDeletion: true
    controller: true
    kind: MachinePool
    name: am-clusterctl-eks-2-pool-0
    uid: c4721a8a-a456-434c-8e3f-a5722a5ffb13
  resourceVersion: "200264"
  uid: d224aca6-da5e-4788-8fa6-c727ace79c25
spec:
  nodeType: al2023
status:
  conditions:
  - lastTransitionTime: "2025-06-17T03:37:53Z"
    status: "True"
    type: Ready

• Generated bootstrap data:

value: |-
  MIME-Version: 1.0
  Content-Type: multipart/mixed; boundary="//"

  --//
  Content-Type: application/node.eks.aws

  ---
  apiVersion: node.eks.aws/v1alpha1
  kind: NodeConfig
  spec:
    cluster:
      apiServerEndpoint: https://xxxxxxxx.xxx.ap-south-1.eks.amazonaws.com
      certificateAuthority: xxxxx
      cidr: 10.96.0.0/12
      name: default_am-clusterctl-eks-2-control-plane-2
    kubelet:
      config:
        maxPods: 110
        clusterDNS:
        - 10.96.0.10
      flags:
      - "--node-labels=eks.amazonaws.com/nodegroup-image=ami-0930ab0e58973e126,eks.amazonaws.com/capacityType=ON_DEMAND,eks.amazonaws.com/nodegroup=am-clusterctl-eks-2-pool-0-bootstrap"

  --//--

• AWSMMP

apiVersion: infrastructure.cluster.x-k8s.io/v1beta2
kind: AWSManagedMachinePool
metadata:
  annotations:
    kubectl.kubernetes.io/last-applied-configuration: |
      {"apiVersion":"infrastructure.cluster.x-k8s.io/v1beta2","kind":"AWSManagedMachinePool","metadata":{"annotations":{},"name":"am-clusterctl-eks-2-pool-0","namespace":"default"},"spec":{"amiType":"CUSTOM","awsLaunchTemplate":{"ami":{"id":"ami-0930ab0e58973e126"},"instanceType":"t3.large","sshKeyName":"spectro2024"},"scaling":{"maxSize":5,"minSize":1}}}
  creationTimestamp: "2025-06-16T12:26:26Z"
  finalizers:
  - awsmanagedmachinepools.infrastructure.cluster.x-k8s.io
  generation: 4
  labels:
    cluster.x-k8s.io/cluster-name: am-clusterctl-eks-2
  name: am-clusterctl-eks-2-pool-0
  namespace: default
  ownerReferences:
  - apiVersion: cluster.x-k8s.io/v1beta1
    blockOwnerDeletion: true
    controller: true
    kind: MachinePool
    name: am-clusterctl-eks-2-pool-0
    uid: c4721a8a-a456-434c-8e3f-a5722a5ffb13
  resourceVersion: "200257"
  uid: 20954503-d2eb-430f-933f-977a70f9cba3
spec:
  amiType: CUSTOM
  awsLaunchTemplate:
    ami:
      id: ami-0930ab0e58973e126
    instanceType: t3.large
    marketType: OnDemand
    sshKeyName: sshkey
  capacityType: onDemand
  eksNodegroupName: default_am-clusterctl-eks-2-pool-0
  providerIDList:
  - aws:///xxxx/i-07142dfb97c7exxxx
  - aws:///xxxx/i-0ef83e9b00a9fxxxx
  roleName: eks-nodegroup.cluster-api-provider-aws.sigs.k8s.io
  scaling:
    maxSize: 5
    minSize: 1
  updateConfig:
    maxUnavailable: 1
status:
  conditions:
  - lastTransitionTime: "2025-06-17T03:37:52Z"
    status: "True"
    type: Ready

Impact

These changes allow users to use launch templates with AL2023 images. Also to specify custom AMIs through launch templates while maintaining compatibility with CAPA's auto AMI lookup mechanism.

Related Issues

Fixes #5546

What type of PR is this?

/kind feature

What this PR does / why we need it:

Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #

Special notes for your reviewer:

Checklist:

• squashed commits
• includes documentation
• includes emoji in title
• adds unit tests
• adds or updates e2e tests

Release note:

EKSConfig now supports generating MIME-formatted bootstrap data for AL2023 nodes using nodeadm and Launch Templates via AWSManagedMachinePool.

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign neolit123 for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[k8s-ci-robot]

Hi @AmitSahastra. Thanks for your PR.

I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[fiunchinho]

/ok-to-test

[AmitSahastra]

/test pull-cluster-api-provider-aws-e2e-blocking
/test pull-cluster-api-provider-aws-apidiff-main
/test pull-cluster-api-provider-aws-test

[k8s-ci-robot]

@AmitSahastra: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
pull-cluster-api-provider-aws-test	1521250	link	true	/test pull-cluster-api-provider-aws-test

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.