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
Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment
Tell us about your request
Graduate IAMIdentityMapping to general availability
Which service(s) is this request for?
EKS
Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?
Declaratively define rules for mapping IAM principals to Kubernetes users and groups, using the Kubernetes API. This API is alpha so I'm wary to recommend it to customers.
Are you currently working around this issue?
Managing the aws-auth ConfigMap instead. This is a single point of co-ordination; it would be nice to set up EKS to also support IAMIdentityMappings.
Additional context
Example manifest for an IAMIdentityMapping:
Community Note
Tell us about your request
Graduate
IAMIdentityMapping
to general availabilityWhich service(s) is this request for?
EKS
Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?
Declaratively define rules for mapping IAM principals to Kubernetes users and groups, using the Kubernetes API. This API is alpha so I'm wary to recommend it to customers.
Are you currently working around this issue?
Managing the
aws-auth
ConfigMap instead. This is a single point of co-ordination; it would be nice to set up EKS to also support IAMIdentityMappings.Additional context
Example manifest for an
IAMIdentityMapping
:https://github.com/kubernetes-sigs/aws-iam-authenticator/blob/master/deploy/example-iamidentitymapping.yaml
The text was updated successfully, but these errors were encountered: