No Auth Provider Found
- Dominant language
- Go
- Stars
- 1k
- Forks
- 121
- PR merge metrics
- No merged PRs in 30d
Description
I am trying to use `mapkubeapis` and am receiving the following error:
```
helm mapkubeapis --dry-run --namespace --kubeconfig /Users/nat-ray/.kube/config --kube-context
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.
Contributor guide
Research direction
Start by reproducing the shown `helm mapkubeapis --dry-run` command with the OIDC-backed context, then compare its authentication behavior with the working `kubectl` and Helm commands. Trace the release query that reports `no Auth Provider found for name "oidc"`; done means the plugin can query the release using that context or clearly reports the required configuration.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, helm, kubernetes
- Domain
- authentication, cli
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100