stackabletech / stackabletech/stackablectl
Store how to uninstall a release in-cluster
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 10
- Forks
- 5
- Avg merge
- 4h 41m
- Merged PRs (30d)
- 4
Description
Currently, stackable release uninstall requires users to specify the last release that they have installed, with undefined behaviour if the specified release doesn't match the installed release.
Ideally, stackablectl should automatically figure out which stackable operators were installed and how to uninstall them.
Contributor guide
No contributing guide indexed for this repository
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 at the stackable release uninstall CLI command and trace how the release argument is currently consumed. Investigate how installed Stackable operators and their release information can be identified in the cluster. Done means uninstall can determine the installed operators and release without requiring users to specify the last release.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes, rust
- Domain
- cli, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100