open-policy-agent / open-policy-agent/cert-controller
Allow for coordinated rotation of keys across multiple pods
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 109
- Forks
- 49
- Avg merge
- 19h 20m
- Merged PRs (30d)
- 6
Description
This is blocked on #27
We should have the ability for one centralized process to manage the key rotation, so that it can be done in a gradual manner.
The alternative would be to have some sort of leader election to figure out which pod is managing key rotation.
We may want to support both models, given that different consumers may have different hosting schemes and availability requirements.
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 issue #27, which blocks this work, then clarify the coordination model for key rotation across pods. Done would require an agreed design and implementation for gradual centralized rotation, leader election, or both, with the hosting and availability requirements resolved.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- distributed-systems, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100