Describe the bug
When creating an AccessEntry to be used by nodes provisioned by Karpenter autoscaler, the ACK resource keeps in this state:
status:
ackResourceMetadata:
arn: arn:aws:eks:us-east-1:012345678910:access-entry/cluster-eks-nprd-pnu0001324-s7/role/759021108710/karpenter-node-role-cluster-eks-nprd-pnu0001324-s7/f8c8bdf0-4831-b76a-5b34-b465b3bd4b6d
ownerAccountID: "012345678910"
region: us-east-1
conditions:
- message: |-
InvalidParameterException: This operation can only be performed on Access Entries with a type of "STANDARD".
{
RespMetadata: {
StatusCode: 400,
RequestID: "db318416-8193-4f94-b553-0180a150b89e"
},
Message_: "This operation can only be performed on Access Entries with a type of \"STANDARD\"."
}
status: "True"
type: ACK.Recoverable
- lastTransitionTime: "2024-08-23T12:15:53Z"
message: Unable to determine if desired resource state matches latest observed
state
reason: |-
InvalidParameterException: This operation can only be performed on Access Entries with a type of "STANDARD".
{
RespMetadata: {
StatusCode: 400,
RequestID: "db318416-8193-4f94-b553-0180a150b89e"
},
Message_: "This operation can only be performed on Access Entries with a type of \"STANDARD\"."
}
status: Unknown
type: ACK.ResourceSynced
createdAt: "2024-08-22T20:56:40Z"
modifiedAt: "2024-08-22T20:56:40Z"
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:
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.
$ k get accessentry -A
NAMESPACE NAME CLUSTER TYPE USERNAME SYNCED AGE
karpenter eks-sprint6-staging-karpenter-ae cluster-eks-nprd-pnu0001324-s7 EC2_LINUX Unknown 39m
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)
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)