zalando / zalando/postgres-operator
Custom Security Context in postgresql
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 5.2k
- Forks
- 1.1k
- Avg merge
- 2d 16h
- Merged PRs (30d)
- 3
Description
- **Which image of the operator are you using?
postgres-operator:v1.9.0 - **Where do you run it - cloud or metal?
Kubernetes and OpenShift - Type of issue?
feature request
Hi, i checked postgres operator configuration and postgresql manifest, there is no parameter to custom SecurityContext. Parameter additional_pod_capabilities only supports adding capabilities in container level SecurityContex. Actually, i want to custom pod level and container lever SecurityContext, example:
pod level SecurityContext:
securityContext:
fsGroup: 7777
runAsNonRoot: true
runAsUser: 7777
container level SecurityContext:
securityContext:
allowPrivilegeEscalation: false
capabilities:
drop:
- ALL
privileged: false
readOnlyRootFilesystem: true
seccompProfile:
type: RuntimeDefault
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
No source file or test is named. Start by tracing how additional_pod_capabilities and the PostgreSQL manifest are handled for Kubernetes and OpenShift, then identify where pod- and container-level security settings are configured. Done means users can provide the requested pod and container SecurityContext fields through operator configuration.
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
- 38/100