akash-network / akash-network/console
Rollback helm release on failed deployment
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 264
- Forks
- 94
- Avg merge
- 18h 49m
- Merged PRs (30d)
- 297
Description
When deployment is failing the deploy workflow is also failing. Quite often helm release gets stuck in a pending state. We need to improve the relevant workflows to check if this happens on non-successful workflows and roll such helm releases back.
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 locating the deployment workflows and their failure-handling steps. Check how a failed deployment can leave a Helm release pending, then verify that unsuccessful workflows roll the affected release back without masking the deployment failure.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- helm
- Domain
- ci-cd, devops
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100