Getting issue to run helm mapkubeapis on GKE cluster no Auth Provider found for name "gcp"
- Dominant language
- Go
- Stars
- 1k
- Forks
- 121
- PR merge metrics
- No merged PRs in 30d
Description
Getting issue to run helm mapkubeapis on GKE cluster
` helm mapkubeapis XXXX -n XXX
2023/03/15 18:36:58 Release 'XXXXX' will be checked for deprecated or removed Kubernetes APIs and will be updated if necessary to supported API versions.
2023/03/15 18:36:58 Get release 'XXXXX' latest version.
Error: failed to get release 'XXXXX' latest version: query: failed to query with labels: no Auth Provider found for name "gcp"
Error: plugin "mapkubeapis" exited with error`
Contributor guide
Research direction
Start by reproducing the documented `helm mapkubeapis XXXX -n XXX` command against a GKE cluster and inspect how the plugin reaches the reported `no Auth Provider found for name "gcp"` error. The issue names no source file or test; done would be a confirmed resolution that lets the command run on GKE, or clear documentation of the required limitation or setup.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- cli, devops
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100