Suggestion: Native support of OAuth2 for custom ingress management

[daniellavoie]

Describe the enhancement you'd like to see I would suggest supporting Oauth2 natively on the api server rather than relying on the oauth2 proxy.

Enabling OAuth2 forces the uses of the nginx ingress controller as an ingress controller. Not all ingress controllers have support for oauth2 redirect so I understand why this opinion is imposed. I also understand that using the oauth2 proxy was a quick shortcut to bring generic auth support. However, with a native support of Oauth2 from the API Server, the deployment of ingress rresources would be a LOT more simplified and be compatible with other ingress providers (e.g.: we are using traefik).

By managing natively OAuth2 in the API, all opinions and restrictions on the ingress provider would be lifted and reduce the friction to adopt the solution.

[vsukhin]

hey @daniellavoie we have it in our Pro Edition. pinging @TheBrunoLopes