stackabletech / stackabletech/secret-operator
Expire pods when secrets change
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 13
- Forks
- 8
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 10
Description
We already expire autoTls secrets when they're about to expire, and when manually mounted secrets are modified. We should do the same for autoTls (and certManager once #474 is in).
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 locating the existing expiration handling for manually mounted secrets and the path that expires autoTls secrets near expiry. Trace how a secret modification triggers pod expiration, then verify equivalent behavior for changed autoTls secrets; account for certManager only after #474 is in place.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes, rust
- Domain
- infrastructure, security
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100