-
Notifications
You must be signed in to change notification settings - Fork 303
Doesn't work on GKE #2
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
Comments
@kklin Thanks! I'll take a look later today and test it upon GKE. |
@kklin Or would you like to send a PR if importing the auth plugins works for you? |
Sure. I took a quick look: adding the auth plugins fixed the error with parsing the kubeconfig, but it still doesn't work with GKE because the
I would PR the auth plugin fix, but I couldn't figure out the right way to update |
Adding the import statement and run
I need to do some investigation about this problem (solution to access the hostIP&hostPort in GKE from client). |
@kklin Hi, anything blocking? How can I help? |
Kubectl clients connect to GKE using the GCP auth provider. Before, the kubectl-debug plugin would panic because it couldn't find the GCP auth provider -- this commit adds support for all auth providers defined by client-go. Fixes aylei#2.
Kubectl clients connect to GKE using the GCP auth provider. Before, the kubectl-debug plugin would panic because it couldn't find the GCP auth provider -- this commit adds support for all auth providers defined by client-go. Fixes #2.
Hello @aylei,
I see that the issue is closed but I have not found any work around. How did you solve? Thanks |
@gadiener |
@gadiener |
Following the binary instructions for mac installation on the README, I get an issue with tar file: |
I got this error when trying this against a GKE cluster:
I've seen this in my own projects before. It'll probably be fixed by importing the auth plugins: kubernetes/client-go#242 (comment).
The text was updated successfully, but these errors were encountered: