zalando / zalando/postgres-operator
[UI] Support affinity configuration in 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
I am running the operator in a cluster that consists of both AMD64 and ARM64 nodes. Since the operator and UI do not support ARM64, I would like to pin them to the amd64 nodes. This is supported in the helm chart for the operator and the postgresql CRD, but not in the chart for the operator-ui.
I have a fork of the repository and added the affinity block to the operator-ui chart. I could provide a pull request. Would this be of any interest, or is there some reason for the affinity block missing from the operator-ui chart?
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
Inspect the Helm chart for operator-ui and compare its configuration with the affinity blocks already supported in the operator chart and PostgreSQL CRD. Confirm how the chart renders its workload manifests, then verify that the requested affinity configuration is accepted and appears in the rendered output.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- helm, kubernetes
- Domain
- infrastructure
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100