Operator not installing AWS bootstrap provider for NodeAdm

[holgerson97]

What steps did you take and what happened:
[A clear and concise description on how to REPRODUCE the bug.]
I installed the latest version of the provider using Helm into an EKS cluster.

What did you expect to happen:
I expect the operator to install all CRDs provided by CAPA.

Anything else you would like to add:
[Miscellaneous information that will assist in solving the issue.]

Environment:

• Cluster-api-operator version: v0.26.0
• Cluster-api version: 1.12.4
• Minikube/KIND version: -
• Kubernetes version: (use kubectl version): 1.33
• OS (e.g. from /etc/os-release): Bottlerocket_ARM_64

/kind bug
[One or more /area label. See https://github.com/kubernetes-sigs/cluster-api-operator/labels?q=area for the list of labels]

core:
  cluster-api:
    version: v1.12.4
    namespace: cluster-api
    createNamespace: true
    manager:
      featureGates:
        ClusterTopology: true

addon:
  helm:
    version: v0.6.1
    namespace: caaph-system
    createNamespace: true

infrastructure:
  aws:
    version: v2.10.2
    namespace: capa-system
    createNamespace: true
    manager:
      featureGates:
        EKSEnableIAM: true
        ClusterTopology: true
        MachinePool: true
        MachinePoolMachines: true
    configSecret:
      name: capa-manager-bootstrap-credentials

manager:
  featureGates:
    core:
      ClusterTopology: true
    aws:
      EKSEnableIAM: true


replicaCount: 2

[k8s-ci-robot]

This issue is currently awaiting triage.

If CAPI Operator contributors determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Details

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.