kube-oidc-proxy icon indicating copy to clipboard operation
kube-oidc-proxy copied to clipboard

Reverse proxy to authenticate to managed Kubernetes API servers via OIDC.

Results 38 kube-oidc-proxy issues
Sort by recently updated
recently updated
newest added

Hello. Is there a plan of having the helm repository for `kube-oidc-proxy` ? I can not see it https://hub.helm.sh/charts/jetstack and I was not able to find it in the documentation....

Hey, I just noticed a thing this morning: When I try to delete something it hangs indefinitely. I have cancel the command :/ Actually for the moment I noticed that...

I have a working kube-oidc-proxy instance but when I try to run `kubectl exec -it` I get a failure. Is `kubectl exec -it` supported by the proxy? Here is what...

https://github.com/jetstack/kube-oidc-proxy/blob/1080bc238c570752b120e9f06584d8131149a27f/deploy/charts/kube-oidc-proxy/templates/deployment.yaml#L63 Hello, I've found an error on the helm chart. I was trying to deploy it with a requiredClaim and end up with the following error: ![image](https://user-images.githubusercontent.com/37403016/114314212-18974380-9afa-11eb-8747-d9bbcd12492b.png) The cli argument...

I am trying to configure Kubernetes Dashboard to use this proxy because I have setup Dex on EKS and am using this to authenticate using OIDC. But I have setup...

Add service.additionalSpec options to helm chart. **UseCase**: NodePort with ExternalDNS: Only get IP's for k8s nodes running kube-oidc-proxy pods (not all nodes in cluster). ``` service: additionalSpec: externalTrafficPolicy: Local ```

dco-signoff: no
size/S
do-not-merge/release-note-label-needed
needs-ok-to-test

https://github.com/aws/containers-roadmap/issues/166#issuecomment-778519901 I will try ASAP and update if it works. If so, that means `kube-oidc-proxy` should not be needed anynore for EKS 🎉 Even though it's a great tool and...

Hi, I wonder if we have or plan to have a prometheus /metrics endpoint? Thanks

I have deployed kube-oidc-proxy and authenticating using Keycloak into our K8s cluster. But I have observed that kube-oidc-proxy takes claims only from refresh_token and not from id_token. e.g refresh_token given...

every token generated have exp for 1h, not sure how we can configure it differently