mapkubeapis failing on helm version "v3.4.2"
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 1k
- Forks
- 121
- PR merge metrics
- No merged PRs in 30d
Description
Hi
I was delighted to find this tool, but for some reason it doesn't work for me.
Can you please advise?
Thanks
Ariela
helm mapkubeapis rel-name --namespace ns-name --dry-run
2023/06/19 15:27:17 NOTE: This is in dry-run mode, the following actions will not be executed.
2023/06/19 15:27:17 Run without --dry-run to take the actions described below:
2023/06/19 15:27:17
2023/06/19 15:27:17 Release 'rel-name' will be checked for deprecated or removed Kubernetes APIs and will be updated if necessary to supported API versions.
2023/06/19 15:27:17 Get release 'rel-name' latest version.
Error: failed to get release 'rel-name' latest version: query: failed to query with labels: exec plugin: invalid apiVersion "client.authentication.k8s.io/v1alpha1"
Error: plugin "mapkubeapis" exited with error
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the shown mapkubeapis command with Helm v3.4.2 and inspect how the plugin obtains the release through the Kubernetes client. Trace the exec-plugin apiVersion error to the relevant dependency or integration point; done means the command completes without this failure and the behavior is covered by an appropriate regression check.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, helm, kubernetes
- Domain
- cli, devops
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100