leland knight

also experiencing this ... probably just going to reinstall and start over

I discovered regexDomainFilter which let me solve my issue specific to the Infoblox provider, so, the above is not needed anymore in my use case. ... But I wonder if...

Post your oauth2-proxy config & the ingress you have configured for your target app.

trying to get the same thing to work ... watching with attention

did it prompt you to log in? what are you using as your identity provider? dex? keycloak? azure? oidc?

there is an oauth2-proxy provider 'keycloak-oidc' and also 'oidc'. If you are using 'keycloak-oidc' try using 'oidc' instead. ``` # in this case oauth2-proxy is going to visit oidc_issuer_url="https://keycloak.vc-prod.k.home.net/auth/realms/home" provider="oidc"...

an older example: https://github.com/oauth2-proxy/oauth2-proxy/issues/1617

Not official support, but just happened to come across your ticket. Have you tried: ``` nginx.ingress.kubernetes.io/auth-signin: "https://oauth2-proxy.vc-prod.k.home.net/oauth2/start?rd=$escaped_request_uri" ```

Closing as oidc example was said to not be deprecated and it works.

Closing. I'm not sure of the details, but after upgrading from 0.11.0 to 0.12.2 metrics server immediately installed and started working. Also, a namespace which wouldn't delete because of something...