You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After about hour and half, using credentials_json is not effective. in the same workflow job.
I understand using token has timelimit, but as i understand credentials_json should not have timelimit.
Expected behavior
Be able to preform actions as "kubectl get pods" using credentials_json even after long period of time in the same job.
Observed behavior
i have a workflow with one job. and few steps.
everything working fine, if for example the steps of watch logs take 20-30 minutes.
but if it takes hour and half for example,
then the last step "get pods" gets error of error: You must be logged in to the server (Unauthorized)
and the step remove chart gets error of Error: Kubernetes cluster unreachable: the server has asked for the client to provide credentials
Thank you for opening an issue. Our team will triage this as soon as we can. Please take a moment to review the troubleshooting steps which lists common error messages and their resolution steps.
Hi @ShaiShalevSQream - this is an issue with get-gke-credentials, not auth. If you don't use the auth plugin (use_auth_provider), then get-gke-credentials generates an OAuth access token and puts it in the Kubeconfig.
You can either refresh auth before running kubectl get po (by using the get-gke-credentials action again) or install and use the auth plugin which handles refreshes.
TL;DR
After about hour and half, using credentials_json is not effective. in the same workflow job.
I understand using token has timelimit, but as i understand credentials_json should not have timelimit.
Expected behavior
Be able to preform actions as "kubectl get pods" using credentials_json even after long period of time in the same job.
Observed behavior
i have a workflow with one job. and few steps.
everything working fine, if for example the steps of watch logs take 20-30 minutes.
but if it takes hour and half for example,
then the last step "get pods" gets error of
error: You must be logged in to the server (Unauthorized)
and the step remove chart gets error of
Error: Kubernetes cluster unreachable: the server has asked for the client to provide credentials
Action YAML
Log output
Additional information
My runner are self hosted runners. using runner-scale-set.
The text was updated successfully, but these errors were encountered: