zalando / zalando/postgres-operator
Missing option for pod labels in the postgres-operator-ui Chart
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-ui:v1.10.1
- Where do you run it - cloud or metal? Kubernetes or OpenShift? Bare Metal K8s
- Are you running Postgres Operator in production? yes
- Type of issue? Feature Request
The helm chart for the postgres-operator has options for setting the pod labels,
eg.
- https://github.com/zalando/postgres-operator/blob/45489d3741b1b956c84e4779edbfd27a26970d9e/charts/postgres-operator/values.yaml#L14
- https://github.com/zalando/postgres-operator/blob/45489d3741b1b956c84e4779edbfd27a26970d9e/charts/postgres-operator/templates/deployment.yaml#L31
This option is missing in the charts for the postgres-operator-ui, and I'd like to see it here.
Reasoning: We internally control firewalling to the api-server with labels, and without the right label access is denied.
Should I open a PR for this issue?
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 inspecting the postgres-operator-ui Helm chart's values and deployment templates, using the referenced postgres-operator values.yaml and deployment.yaml as a comparison. The work is done when pod labels can be configured through the UI chart and appear on its rendered deployment.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- helm, kubernetes
- Domain
- devops, infrastructure
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100