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

Doesn't work with GKE #62

Open
TonyBogdanov opened this issue Jan 22, 2024 · 4 comments
Open

Doesn't work with GKE #62

TonyBogdanov opened this issue Jan 22, 2024 · 4 comments
Labels
bug Something isn't working

Comments

@TonyBogdanov
Copy link

I have a GKE cluster that appears automatically when I open k8studio. Double clicking on it, however, shows an error toast and nothing else happens:

image

@mo-othman mo-othman added the bug Something isn't working label Jan 23, 2024
@mo-othman
Copy link
Collaborator

Hi @TonyBogdanov, Thanks for reporting this, I will do a similar setup and investigate. I have a question

  • Are you using an admin user? if not, Could you provide an idea of the user's IAM permissions if you don't mind

This information will help me reproduce the issue more efficiently and faster. Thanks!

@TonyBogdanov
Copy link
Author

Actually when I opened k8studio I saw my cluster listed and double clicked on it. I never setup the connection and I have no setup on my computer. I do have a ~/.kube/config file on WSL, maybe that's what k8studio is picking up somehow?

The correct way would probably be to setup the connection manually. Do you have any guide how to obtain credentials from GKE to be used in k8studio?

@mo-othman
Copy link
Collaborator

The application by default reads your default kubeconfig file. If you're working with Google Kubernetes Engine (GKE), you can update your kubeconfig file using the following command:
gcloud container clusters get-credentials CLUSTER_NAME --region=COMPUTE_REGION
For more information on how gcloud container clusters get-credentials works, you can refer to the documentation https://cloud.google.com/sdk/gcloud/reference/container/clusters/get-credentials. Additionally, GKE-specific documentation on cluster access: https://cloud.google.com/kubernetes-engine/docs/how-to/cluster-access-for-kubectl

We're currently working on enhancing the process of adding clusters by redesigning the workflow. The upcoming approach will allow you to seamlessly add multiple configuration files instead of using the form modal. This change aims to provide more flexibility and convenience in managing your clusters.

@vlakarados
Copy link

vlakarados commented Jan 25, 2024

Same issue here, using several clusters from AWS as well as a couple of other ones.
Windows 11, WSL2.
Used to use k9s and it still works properly, while K8SStudio did load clusters, same error "cannot read properties of null" when clicking on cluster on the dashboard as Tony has.

[2024-01-25 15:26:06.449] [info]  Clusters config created
[2024-01-25 15:26:07.716] [info]  Selecting Cluster arn:aws:eks:eu-central-1:xxx:cluster/core
[2024-01-25 15:26:07.719] [info]  Loading Cluster arn:aws:eks:eu-central-1:xxx:cluster/core
[2024-01-25 15:26:07.749] [error] Cannot read properties of null (reading 'toString')
[2024-01-25 15:26:07.750] [error] Cannot read properties of null (reading 'toString')
[2024-01-25 15:26:07.751] [error] Error Loading cluster Cannot read properties of null (reading 'toString')

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants