mapkubeapis looks on last deployment but helm looks on last non-failed deployment
- Dominant language
- Go
- Stars
- 1k
- Forks
- 121
- PR merge metrics
- No merged PRs in 30d
Description
I had today a situation where a helm deployment had such history:
Revision 1 - status deployed
Revision 2 - status failed
Revision 3 - status failed
I run `helm mapkubeapis NAME_OF_RELEASE` and it showed that there were no changes needed.
Then I run `helm upgrade --install` and it faield that PDB has version policy/v1beta1.
It seems that helm tries to upgrade from last successful revision, but helm-mapkubeapis takes into account only last one.
As a workaround I deleted form kubernetes secrets of helm releases that are failed and run `helm mapkubeapis NAME_OF_RELEASE`
Contributor guide
Research direction
Start by reproducing the reported release history with one deployed revision followed by failed revisions, then compare helm mapkubeapis with helm upgrade --install when selecting a revision. The change is done when mapkubeapis examines the last non-failed deployment and maps the deprecated PDB API so the subsequent upgrade succeeds.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, helm, kubernetes
- Domain
- devops, infrastructure, release
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100