stackabletech / stackabletech/secret-operator
Expire pods when `k8sSearch` secrets are modified
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 13
- Forks
- 8
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 10
Description
Postponed from https://github.com/stackabletech/secret-operator/pull/114
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 by reviewing the linked pull request #114, since the issue says this work was postponed from there. Identify the intended handling for modified k8sSearch secrets and the affected pod lifecycle before locating the relevant Rust operator entry points. Done means the postponed behavior is clearly implemented and verified against the repository's existing tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes, rust
- Domain
- devops, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100