-
Notifications
You must be signed in to change notification settings - Fork 669
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
Support ingress.kubernetes.io/auth-{type,secret,realm} #68
Comments
Without this there is no (easy) way to protect ingress endpoints with oauth2. https://eng.fromatob.com/post/2017/02/lets-encrypt-oauth-2-and-kubernetes-ingress/ |
Would be great to have the equivalent of
|
@projectcontour/maintainers superceded by #2664 ? given our investment is more in HTTPProxy and Gateway API |
For anyone landing here my project now supports contour (so oauth, oidc, jwt, etc, etc). https://github.com/travisghansen/external-auth-server |
Yes, I think this one is superseded by #2664, thanks for finding this issue. And that's great to hear @travisghansen, thanks! Being able to look at another implementation will be very helpful for the inline filter version. |
Yeah, happy to work with you on design if it’s helpful. |
Fixes #68 Signed-off-by: Steve Sloka <slokas@vmware.com>
Add support for
ingress.kubernetes.io/auth-type
ingress.kubernetes.io/auth-secret
ingress.kubernetes.io/auth-realm
Annotations.
The text was updated successfully, but these errors were encountered: