Failed to Create an AccessEntry for Karpenter Node Role #2144
Labels
kind/bug
Categorizes issue or PR as related to a bug.
service/eks
Indicates issues or PRs that are related to eks-controller.
Describe the bug
When creating an AccessEntry to be used by nodes provisioned by Karpenter autoscaler, the ACK resource keeps in this state:
Checking in CloudTrail, its possible to see that the AccessEntry was created, but the ack-eks-controller is trying to update it, which is not allowed:
Successful creation:
Failed update tentative by ack:
The YAML definition for the AccessEntry hasn't being changed and is as follows:
Its getting deployed in the cluster by FluxCD using Kustomization.
Steps to reproduce
Just deploy the resource in the cluster. It never turns to the True SYNCED state.
Expected outcome
The resource with a True SYNCED state in the cluster.
Environment
eks-controller version: 1.4.4
Kubernetes version
1.30
Using EKS (yes/no), if so version?
Yes.
eks.6
AWS service targeted (S3, RDS, etc.)
EKS (AccessEntry)
The text was updated successfully, but these errors were encountered: