Error: no Auth Provider found for name "gcp" about kubecm HOT 9 CLOSED

Hi @sunny0826,

There's no much more to say about it, really.

The configuration I reproduce here is a sanitized version of that config file, where I only removed the tokens and trimmed the tail of gke_cluster to remove sensible information -- everything else is exactly the same.

I realize tho that I haven't provided the command I issued when I got the error nor the full error output, so here it goes:

~ ✖1 ❯ k get ns
NAME                  STATUS   AGE
default               Active   295d
gitlab-managed-apps   Active   233d
kube-node-lease       Active   295d
kube-public           Active   295d
kube-system           Active   295d

~ took 6s ❯ kubecm ns kube-public
Error: no Auth Provider found for name "gcp"
Usage:
  kubecm namespace [flags]

Aliases:
  namespace, ns

Examples:

# Switch Namespace interactively
kubecm namespace
# or
kubecm ns
# change to namespace of kube-system
kubecm ns kube-system


Flags:
  -h, --help   help for namespace

Global Flags:
      --config string   path of kubeconfig (default "/Users/cig0/.kube/config")

no Auth Provider found for name "gcp

~ ✖1 ❯ kubecm ns
Error: no Auth Provider found for name "gcp"
Usage:
  kubecm namespace [flags]

Aliases:
  namespace, ns

Examples:

# Switch Namespace interactively
kubecm namespace
# or
kubecm ns
# change to namespace of kube-system
kubecm ns kube-system


Flags:
  -h, --help   help for namespace

Global Flags:
      --config string   path of kubeconfig (default "/Users/cig0/.kube/config")

no Auth Provider found for name "gcp"

from kubecm.

I could help you with that part, let me know if you need me to test anything.

Incidentally if you happen to have access to GCP, you should be able to open a free-tier account: https://cloud.google.com/free

from kubecm.

Did this error occur in older versions?
This error is thrown by client-go.

from kubecm.

for your kubeconfig, your context named gke_cluster, Can you describe your operation in detail?

from kubecm.

This issue appears to be an authentication issue with client-go, thank you for the tip, I will try to fix this.

from kubecm.

This problem looks very similar to kubernetes/client-go#242, but I don't have GKE to test whether following the approach in ISSUE solves the problem.

from kubecm.

Thanks for the tip, Happy new year!

from kubecm.

I've just tried to fix this on the master branch, can you pull the code from the master branch, compile and test it?

from kubecm.

You can try the v0.13.1 version and look forward to your feedback.

from kubecm.