-
Notifications
You must be signed in to change notification settings - Fork 320
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[EKS] [aws-iam-authenticator]: Add aws-iam-authenticator as a CRD #550
Comments
Would be nice to have this feature in EKS. Using the configmap to manage users is a pain right now. Is there an ETA? |
This has been in aws-iam-authenticator for a while now: How can this be enabled in EKS? |
If you need a solution supporting CRDs with EKS, please have a look at https://github.com/rustrial/aws-eks-iam-auth-controller, I use it for all my EKS clusters. It uses the CRDs (API) from aws-iam-authenticator and therefore is compatible with aws-iam-authenticator. |
An AWS feature that is is not available for EKS :( |
Addressed with #185 |
Hi @mikestef9, can this please be reopened? the way this was resolved is very ISV-unfriendly |
I have to disagree this was addressed with #185. The ask is to automate this using K8s/EKS primitives |
Would using ACK in conjunction with #185 meet your requirements? https://aws-controllers-k8s.github.io/community/reference/eks/v1alpha1/accessentry/ |
Tell us about your request
Add aws-iam-authenticator as a CRD on EKS
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?
kubernetes-sigs/aws-iam-authenticator#79
Are you currently working around this issue?
Using aws-iam-authenticator with kubectl
The text was updated successfully, but these errors were encountered: