Open alam0rt opened 2 months ago
This issue is currently awaiting triage.
If CAPA/CAPI 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.
/assign
/kind bug
What steps did you take and what happened: [A clear and concise description of what the bug is.]
The
capa
client-go is failing to listv1beta1.MachineDeployments
which is in turn causing theiamauth
controller to error out before it can reconcile.The cluster in question does not use any machine deployments (its an EKS fargate cluster).
What did you expect to happen:
For the
iamauth
controller to get an empty list of machine deployments and continue reconciliation.Anything else you would like to add: [Miscellaneous information that will assist in solving the issue.]
Appears to be occurring here: https://github.com/kubernetes-sigs/cluster-api-provider-aws/blob/c2c96dd3d11d57cd2dfa4faaf28f7476c4a2a005/pkg/cloud/services/iamauth/reconcile.go#L125-L128
Environment:
kubectl version
): v1.30.3-eks-a18cd3a/etc/os-release
): Fargate / bottlerocket