helm/helm-mapkubeapis

No Auth Provider Found

nat-ray opened this issue · 6 comments

I am trying to use mapkubeapis and am receiving the following error:

helm mapkubeapis --dry-run --namespace <namespace> --kubeconfig /Users/nat-ray/.kube/config --kube-context <context-name>  <helm-chart-name>
2023/04/13 11:01:52 NOTE: This is in dry-run mode, the following actions will not be executed.
2023/04/13 11:01:52 Run without --dry-run to take the actions described below:
2023/04/13 11:01:52
2023/04/13 11:01:52 Release 'rabbitmq-bitnami' will be checked for deprecated or removed Kubernetes APIs and will be updated if necessary to supported API versions.
2023/04/13 11:01:52 Get release 'helm-chart-name' latest version.
Error: failed to get release 'helm-chart-name' latest version: query: failed to query with labels: no Auth Provider found for name "oidc"
Error: plugin "mapkubeapis" exited with error
  1. All of my other helm commands work well.
  2. All of my kubectl commands in this context work well.
  3. I have tried setting the KUBECONFIG environment variable and running with the --kube-context flag, but the result is the same.
  4. I have tried updating the plugin using helm plugin update mapkubeapis.
  5. I have tried uninstalling and reinstalling the plugin.

Is there something I am missing? Thank you.

Same issue on v0.4.1 but not on v0.3.2

If you're seeing this I think you may need to update to the new kubectl auth plugin for gke:

https://cloud.google.com/blog/products/containers-kubernetes/kubectl-auth-changes-in-gke

The error I received was Error: failed to get release 'acme-foo' latest version: query: failed to query with labels: no Auth Provider found for name "gcp" and updating the kubectl auth plugin for gke resolved the issue. I'm not sure if this applies to the original issue which was a slightly different error (oidc vs gcp).

Are there any updates?

I have the same error as @macropin but for provider "oidc". Removed 0.4.1 and installed 0.3.2 It works fine.

Unmerged fix here: #115