stackabletech / stackabletech/secret-operator
Explicit CA rotation
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 13
- Forks
- 8
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 10
Description
#93 implemented implicit CA rotation when the CA certificate is about to expire, but it would be useful to have a way to initiate it manually (such as for #465).
One way to do this would be to add an annotation to the CA Secret that overrides the certificates' notBefore (expiration) time for renewal purposes. This way, you could request "replace this CA in a week", causing a new CA to be provisioned immediately, and provisioning using the old one to stop after about a week (still leaving a clean migration window, though shortened compared to the regular one).
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 implicit CA rotation implemented for #93 and the CA Secret handling, then compare the requested behavior with the migration scenario in #465. Define how a manual renewal annotation affects provisioning and the migration window; done means the behavior and its edge cases are specified and covered by tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes, rust
- Domain
- backend, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100