-
Notifications
You must be signed in to change notification settings - Fork 297
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
User: <username> does not have appropriate auth credentials in kubeconfig #226
Comments
You need to add code here: That adds support for the GKE authProvider. In truth, that code should really be abstracted out into a generic |
@brendanburns please do not close it. This issue is a request for step-by-step instruction. Meaning someone who knows and understands Kubernetes, Kubernetes-Client and Google Cloud Kubernetes Engine should review it and document it. Based on what you provided, I did add the code below
and ran the code below.
Unfortunately |
in here
and And service account has the necessary permission |
That code looks correct. I suspect that your authentication token is expired or some such. See the code here: For checking for expiration in Java. If you want to track implementing auth for GKE, please file a separate issue (similar to #135 but for GKE auth) I think that the code that you wrote above should be correct, but I don't have a GKE cluster to test on, I know that the Java code in |
You were right. It is an expired token issue. Upon your message, I ran Since AKS refresh token is left as NotImplemented, I did the same thing for GKE and added a pull request so at least existing library supports both platform without refresh token parts now. |
fixes #226 neither GCP one nor Azure one supports renew expired token feature
Examples are based on
where it doesn't work out of the box and according to #91 workaround is simply
for development environment.
What is the step-by-step instruction to make this work on production environment for Kubernetes on Google (meaning no
kubectl proxy
workaround )The text was updated successfully, but these errors were encountered: