search

jetstack / kube-oidc-proxy

Reverse proxy to authenticate to managed Kubernetes API servers via OIDC.
https://jetstack.io
Apache License 2.0
477 stars 93 forks source link

exec into the pod exits automatically with no error code using kubeconfig file generated from kube-oidc-proxy, gangway & keycloak #179

Closed Yukesh4791 closed 3 years ago

Yukesh4791 commented 3 years ago

Hi everyone, recently I have deployed kube-oidc-proxy using Gangway and Keycloak into our K8s cluster. Though I have deployed it successfully, but whenever I try to do exec into a pod using token(kubeconfig file) generated from Gangway-keycloak, within few minutes the pod is exited automatically with no error code. The same behaviour is observed when we deployed kube-oidc-proxy with Gangway and Dex. Not sure about the cause of this issue.

In keycloak, I don't find any token expiry parameters. And kube-oidc-proxy logs doesn't say anything.

This doesn't happen when we use eks generated kubeconfig file.

Please find the attached screenshot. MicrosoftTeams-image

Any solution to get rid of this will be much appreciated.

Yukesh4791 commented 3 years ago

Update: this was happening because of timeout at load balancer. After adding additional annotations for timeout in ingress, the issue is fixed.

ref: https://github.com/kubernetes/kubernetes/issues/59411#issuecomment-363386735