-
Notifications
You must be signed in to change notification settings - Fork 561
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
Cannot analyze GKE environment #133
Comments
Hello @hapham1701! Unfortunately, I could not reproduce your issue. Authenticated on a cluster using
and could analyze without problems. Please provide a bit more information on your configuration, e.g., some obfuscated information about your kube context. Thank you! |
this is full error: goroutine 1 [running]: |
As written before, please add some more information about your configuration. e.g. kubectl config view (for your current context). |
If you could print your |
result : cat ~/.k8sgpt.yaml backend_type: openai |
@hapham1701 Do you have gcloud properly installed/configured on your environment ? |
This is information about gcloud and kubectl, which i have already installed on my laptop. Please feel free to ask me if you need any further information: gcloud version Google Cloud SDK 423.0.0 To take a quick anonymous survey, run: ~ kubectl version Server Version: version.Info{Major:"1", Minor:"24", GitVersion:"v1.24.9-gke.3200", GoVersion:"go1.18.9b7", Compiler:"gc", Platform:"linux/amd64"} |
Hi @thschue This is the result of the command: kubectl config view
|
@hapham1701 can you try to run : |
I have set up a clean environment on Debian, and I had no issues.
Here's my configuration:
Here's my version of gcloud:
I think you need to use |
Here's my version of gcloud: ~ gcloud version After install gke-gcloud-auth-plugin, The error still exists. |
It worked after I upgraded ver chatgpt to 0.1.6 and ran the command 'gcloud container clusters get-credentials xxx --region xxx --project xxx'. I don't know why I needed to get credentials even though they already existed. |
I experienced the same problem, but I can confirm that it is recovered by installing and activating the
A change in the kubectl authentication method causes this problem. You can read the details in the following document. |
I'm facing this issue while running command: k8sgpt analyze on Macos arm64 and connecting to GKE.
Error initialising kubernetes client: no Auth Provider found for name "gcp"
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x2 addr=0x0 pc=0x101e6c600]
The text was updated successfully, but these errors were encountered: