Skip to content
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

Open
tblaisot opened this issue Sep 30, 2024 · 5 comments
Open

Unable to connect to GKE cluster from Desktop App #2359

tblaisot opened this issue Sep 30, 2024 · 5 comments
Labels
desktop Issues related to the desktop GKE Related to Google Kubernetes Engine

Comments

@tblaisot
Copy link

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 kubectl

this is the auth part of the kubeconfig for this cluster (generated using gcloud gcloud container clusters get-credentials cluster)

users:
- name: redacted_cluster_name
  user:
    exec:
      apiVersion: client.authentication.k8s.io/v1beta1
      command: gke-gcloud-auth-plugin
      installHint: Install gke-gcloud-auth-plugin for use with kubectl by following
        https://cloud.google.com/kubernetes-engine/docs/how-to/cluster-access-for-kubectl#install_plugin
      provideClusterInfo: true
@dosubot dosubot bot added desktop Issues related to the desktop GKE Related to Google Kubernetes Engine labels Sep 30, 2024
@joaquimrocha
Copy link
Collaborator

Hi @tblaisot . Can you tell us what Headlamp version you are using and on what platform?

@tblaisot
Copy link
Author

Hi,

I forgot to add it sorry.

Version: 0.25.1
Commit: 89e2c59
Package: Flatpak from Flathub
OS: Linux Ubuntu 24.04.1

@joaquimrocha
Copy link
Collaborator

@tblaisot I think this may be the same case as described here:
#1885 (comment)

I will try to get this fixed on our side ASAP.

@tblaisot
Copy link
Author

There is a lot of similarity for sure.

@mevrin-ueat
Copy link

mevrin-ueat commented Oct 1, 2024

@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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
desktop Issues related to the desktop GKE Related to Google Kubernetes Engine
Projects
None yet
Development

No branches or pull requests

3 participants