<p>Could you please provide explanation for what reason <a href="https://github.com/oauth2-proxy/oauth2-proxy" rel="nofollow noreferrer">oauth2-proxy</a> as sidecar can be used?
For example an architecture where every pod in k8s has this sidecar, which proxies to Keycloack.</p>

xeLL
<p>The repo you referred has a readme with a good explanation.</p>
<p>It lets you secure a web app without making any changes to the app itself. The <code>Auth Provider</code> is Keycloak in your case. For example, you can add your organization's auth to a Kubernetes dashboard.</p>
<p>Note that if you're using ingress to expose a service, the oauth2-proxy doesn't have to be sidecar. You can use ingress annotations to route auth requests to a separate pod (or even a separate namespace), like in the nginx-ingress example: <a href="https://kubernetes.github.io/ingress-nginx/examples/auth/oauth-external-auth/" rel="nofollow noreferrer">https://kubernetes.github.io/ingress-nginx/examples/auth/oauth-external-auth/</a>. In this way you reuse one oauth-proxy for multiple apps.</p>
