zalando / zalando/postgres-operator
Support for Pod Security Admission
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 5.2k
- Forks
- 1.1k
- Avg merge
- 2d 16h
- Merged PRs (30d)
- 3
Description
Please, answer some short questions which should help us to understand your problem / question better?
- Which image of the operator are you using?
registry.opensource.zalan.do/acid/postgres-operator:v1.7.1 - Where do you run it - cloud or metal? Kubernetes or OpenShift?
Azure AKS - Are you running Postgres Operator in production? [yes | no]
no, not yet - Type of issue? [Bug report, question, feature request, etc.]
feature request
Are there any plans to support the Pod Security Standards planned for the new k8s Pod Security Admission?
To the best of my knowledge, Spilo already supports running in sufficiently restricted containers, but I haven't found a way to specify a fitting securityContext to allow it to start in a Namespace that enforces restricted.
Contributor guide
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 Kubernetes Pod Security Standards and Pod Security Admission documentation, then inspect the operator and Spilo pod securityContext configuration. Determine which settings prevent startup in a namespace enforcing restricted, and verify that the operator can create and run the required pods under that policy.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes, postgresql
- Domain
- databases, infrastructure, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100