-
Notifications
You must be signed in to change notification settings - Fork 170
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
Unable to connect to GKE cluster from Desktop App #2359
Comments
Hi @tblaisot . Can you tell us what Headlamp version you are using and on what platform? |
Hi, I forgot to add it sorry. Version: 0.25.1 |
@tblaisot I think this may be the same case as described here: I will try to get this fixed on our side ASAP. |
There is a lot of similarity for sure. |
@joaquimrocha got same error on PopOS, I found underlying issue It looks like you are trying to use a client-go credential plugin that is not installed.
To learn more about this feature, consult the documentation available at:
https://kubernetes.io/docs/reference/access-authn-authz/authentication/#client-go-credential-plugins
Install gke-gcloud-auth-plugin for use with kubectl by following https://cloud.google.com/blog/products/containers-kubernetes/kubectl-auth-changes-in-gke
server process stderr: 2024/10/01 11:10:41 http: proxy error: dial tcp 127.0.0.1:44703: connect: connection refused plugin is installed but not using same name ~$ apt list --installed | grep gke-gcloud-auth-plugin
google-cloud-cli-gke-gcloud-auth-plugin/cloud-sdk,now 494.0.0-0 amd64 [installed]
google-cloud-sdk-gke-gcloud-auth-plugin/cloud-sdk,now 467.0.0-0 all [installed]
~$ which gke-gcloud-auth-plugin
/usr/bin/gke-gcloud-auth-plugin hope it will help |
Hello
I am unable to use headlamp to view my GKE cluster.
The probable cause is the auth method.
Since some years GCP have switched to auth using a gcloud plugin.
In my setup, the plugin is installed using gcloud:
gcloud components install gke-gcloud-auth-plugin
and i am able to connect to cluster without a problem using kubectlthis is the auth part of the kubeconfig for this cluster (generated using gcloud
gcloud container clusters get-credentials cluster
)The text was updated successfully, but these errors were encountered: