zalando / zalando/postgres-operator
Can't remove runAsUser from securityContext on helm deployment
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?
-> registry.opensource.zalan.do/acid/postgres-operator:v1.10.1 - Where do you run it - cloud or metal? Kubernetes or OpenShift? [AWS K8s | GCP ... | Bare Metal K8s]
-> OpenShift - Are you running Postgres Operator in production? [yes | no]
-> no - Type of issue? [Bug report, question, feature request, etc.]
-> feature request
I would like to use the helm chart for deploying the postgres operator. There is a problem with your helm chart because i can't create the deployment out of the chart without runAsUser: 1000 from your predefined securityContext.
Actually i have used the manual deployment process for the operator to comment out the runAsUser line.
In OpenShift pods will started with an arbitrary UID. The default SCC do not allow defined UIDs.
Is there a possibility to declare runAsUser as optional?
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 in the Helm chart's deployment securityContext configuration and check how runAsUser is rendered. Make runAsUser optional so the chart can deploy on OpenShift with an arbitrary UID, then verify that the rendered deployment omits it when unset.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- helm, kubernetes, postgresql
- Domain
- databases, devops, infrastructure
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100