-
Notifications
You must be signed in to change notification settings - Fork 145
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
Using dex-k8s-authenticator with AWS EKS #132
Comments
There is good blog regarding option #2 |
Thanks! I saw that yesterday but that seemed a bit complicated. (more pieces into the puzzle) In that case, I'm replacing dex-k8s-authenticator completely with I'll give that a go today, let's see.. |
Ok, I was able to use dex-k8s-authenticator on EKS. This obviously requires kube-oidc-proxy setup, and instead of configuring dex-k8s-authenticator to talk with EKS directly, you configure it to talk with kube-oidc-proxy. It works quite well! |
@jeffisabelle that is great to hear. Would you mind writing something in the docs folder and MR it ? thanks |
Yes, of course. I can create a PR on this weekend with a runbook for the EKS setup. Cheers, |
Hey there, is it possible to use this authenticator with EKS? I was trying to set this up, but apparently it is not possible to update Kubernetes API Server parameters in EKS and thus dex does not work directly with OIDC. [1]
There is also a way to enable dex on EKS with a proxy [2], but I couldn't match the puzzle pieces together.
Has anybody done this before?
1 - aws/containers-roadmap#166
2 - https://github.com/jetstack/kube-oidc-proxy
Thanks!
The text was updated successfully, but these errors were encountered: