zalando / zalando/postgres-operator
SecurityContext configurations are missing for postgres-operator-ui and cluster configurations
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 5.2k
- Forks
- 1.1k
- Avg merge
- 2d 16h
- Merged PRs (30d)
- 3
Description
Hello I am trying to set up postgres-operator in kubernetes cluster. I am using latest version v1.12.2
Apparently I can only configure securityContext for postgres-operator with (allow_privilege_escalation and runAsNonRoot).
But I can not do the same for postgres-operator-ui or for the cluster configuration itself.
So with this issues in place I can not successfully use the operator.
I also saw there are a lot of other issues ongoing related with this. Is there someone working on this issue already or do you plan to add this in the future?
Thanks in advance!
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 by locating the configuration paths for postgres-operator-ui and PostgreSQL cluster resources in the repository, then review how the existing postgres-operator securityContext settings are exposed. Done means both components accept the requested securityContext options and the settings can be used successfully in a Kubernetes cluster.
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