zalando / zalando/postgres-operator
[bug] cannot set `nodeSelector` for postgres-ui Helm chart
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.11.0
- Where do you run it - cloud or metal? Kubernetes or OpenShift? [K3s]
- Are you running Postgres Operator in production? [yes]
- Type of issue? [Bug report/feature request]
Some general remarks when posting a bug report:
- Please, check the operator, pod (Patroni) and postgresql logs first. When copy-pasting many log lines please do it in a separate GitHub gist together with your Postgres CRD and configuration manifest.
- If you feel this issue might be more related to the Spilo docker image or Patroni, consider opening issues in the respective repos.
List of values do not expose nodeSelector in https://github.com/zalando/postgres-operator/blob/master/charts/postgres-operator-ui/values.yaml.
Would it be possible to add those? Thanks.
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 charts/postgres-operator-ui/values.yaml and inspect the postgres-ui Helm chart templates that configure its deployment. Add a configurable nodeSelector value and verify that the rendered chart applies it to the postgres-ui workload.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- helm, kubernetes, postgresql
- Domain
- devops, infrastructure
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100