open-policy-agent / open-policy-agent/cert-controller
Recommended way to configure/run in multi-replica setting
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 109
- Forks
- 48
- Avg merge
- 19h 20m
- Merged PRs (30d)
- 6
Description
I'm looking at using this awesome library in my admission webhook after a long search.
I'm curious if the library has any builtin mechanisms to coordinate first-time cert provisioning or renewals when the webhook itself is deployed as a ReplicaSet with >1 instances (and they race each other and end up with different certs or have write-write conflict on webhookconfiguration caBundle field)?
Or is this concern inherently not valid (maybe because Secrets eventually propagate and processes restart etc)?
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
No files, tests, or entry points are named. Start by tracing certificate provisioning, renewal, and webhookconfiguration updates in the repository, then determine whether multi-replica behavior is supported or needs coordination; done should be a clear, documented recommendation or an agreed implementation scope.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- infrastructure, security
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100