open-policy-agent / open-policy-agent/cert-controller
Use 1 secret per webhook pod to store the public/private key pairs
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 109
- Forks
- 49
- Avg merge
- 19h 20m
- Merged PRs (30d)
- 6
Description
Keeping different secrets for different pods will allow gradual rotation, which will mitigate the downsides of an instantaneous rotation:
- All pods restarting at once
- If the new key is bad, there is no opportunity for admin detection/intervention
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 webhook pod configuration and the code that creates or reads its public/private key secrets. Review how pods currently share keys and how rotation is handled. Done means a documented, tested design for per-pod secrets and gradual rotation, including failure handling.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- infrastructure, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100