You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[EKS Controller] Request to provide an optional field accessEntry in the Capability CR Spec. #3175
Is your feature request related to a problem?
The Capability CR (eks-controller v1alpha1) has no way to refer to, order against, or observe the EKS access entry that belongs to the capability role. That makes it hard to manage the capability's access entry declaratively with the ACK AccessEntry CR.
What exists today (eks-controller v1.26.0 API types):
Capability.spec fields: clusterName/clusterRef, name, type, roleARN/roleRef, configuration, deletePropagationPolicy, tags. Nothing refers to an access entry.
Capability.status has no access entry information (no principal ARN, no access entry ARN).
The AWS CreateCapability API has no access entry parameter either, so the controller cannot forward one.
Per the EKS docs (Create an ACK capability, Security considerations for EKS Capabilities), EKS creates the access entry for the capability role itself, with AmazonEKSACKPolicy (cluster scope). The same docs tell users to associate extra policies to that entry, for example AmazonEKSSecretReaderPolicy for rds, secretsmanager, acm and others.
AccessEntry is keyed by clusterName + principalARN (principalARN is required and immutable). It also has no link to a Capability.
Describe the solution you'd like
Provide a field in the CR Spec of capability to use the accessEntry resource arn .
Describe the use case
We create the capability role, the Capability CR and (ideally) an AccessEntry CR together as one unit, from a single declarative source. We want the capability's access entry (extra access policies, kubernetesGroups) to be owned by an AccessEntry CR. Today we cannot hand the access entry to the Capability CR, and there is no supported ordering between the two:
Describe alternatives you've considered
Adopting the EKS-created entry with an AccessEntry CR that lists AmazonEKSACKPolicy plus the extra policies.
Calling aws eks associate-access-policy out of band . This breaks the declarative flow.
Pre-creating the AccessEntry before the Capability. This is undocumented, and the stale-entry failure mode above is risky.
Hello @yogaraja 👋 Thank you for opening an issue in ACK! A maintainer will triage this issue soon.
We encourage community contributions, so if you're interested in tackling this yourself or suggesting a solution, please check out our Contribution and Code of Conduct guidelines.
You can find more information about ACK on our website.
This is working as designed; the access entry is an element of the Cluster resource. This is a composition use case, where the external dependencies across cloud resources are associated, but are not controller or owned cross-service or cross-resource. It may be worth looking at higher level compositions with kro or a similar approach.
Activity
github-actions commentedon Nov 12, 2026
Hello @yogaraja 👋 Thank you for opening an issue in ACK! A maintainer will triage this issue soon.
We encourage community contributions, so if you're interested in tackling this yourself or suggesting a solution, please check out our Contribution and Code of Conduct guidelines.
You can find more information about ACK on our website.
jlbutler commentedon Nov 17, 2026
This is working as designed; the access entry is an element of the Cluster resource. This is a composition use case, where the external dependencies across cloud resources are associated, but are not controller or owned cross-service or cross-resource. It may be worth looking at higher level compositions with kro or a similar approach.