open-policy-agent / open-policy-agent/frameworks
External Data cabundle should be referenceable from a secret
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 127
- Forks
- 61
- Avg merge
- 1d 17h
- Merged PRs (30d)
- 13
Description
The provider CRD expects the cabundle to be a pem base64 encoded string. Unfortunately, this doesn't work well for using tools like cert manager or vault to manage certs for us.
We should allow the provider CRD to reference Kubernetes secrets and can instruct the controller to load them at runtime. The pattern is followed by other tools like crossplane (specifically here) and even built in the ingress CRD.
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 with the externaldata.gatekeeper.sh Provider CRD definition referenced in the issue, then trace the controller code that reads the provider's cabundle. Compare the secret-reference patterns in Crossplane and the Kubernetes ingress CRD. Done means the Provider CRD can reference a Kubernetes Secret and the controller loads the cabundle at runtime.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- backend, infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100