stackabletech / stackabletech/stackablectl
Add labels for Jobs to mark them as idempotent for stackablectl demo install
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 10
- Forks
- 5
- Avg merge
- 4h 41m
- Merged PRs (30d)
- 4
Description
This is a follow-up issue to https://github.com/stackabletech/stackable-cockpit/issues/333. Only the first suggested solution was implemented there.
The second one states: Add labels to certain jobs that are idempotent (safe to be recreated and run again), and jobs that should be ignored (initial setup jobs, eg: for Keycloak).
This is needed for idempotent demo installations and to minimize the work a developer needs to do to upgrade demos. For more context, check the previous issue.
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
Review the previous issue, stackable-cockpit#333, to understand the first solution and the remaining proposed approach. Identify the demo-install entry points and the relevant Kubernetes Jobs, then add labels distinguishing idempotent jobs from jobs to ignore; done means demo installations can be rerun and upgraded with less manual work.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes, rust
- Domain
- cli, devops
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100