zalando / zalando/postgres-operator
Add nodeSelector and tolerations to postgres-operator-ui chart
Open
Nobody has claimed this yet.
enhancement
help wanted
- 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.8.1
- Where do you run it - cloud or metal? Kubernetes or OpenShift? Scaleway Kapsule
- Are you running Postgres Operator in production? no
- Type of issue? Feature Request
I need to be able to attach ALL Postgres resources to a specific node pool, which at the moment, I can do fine with the exception of the operator's UI.
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 postgres-operator-ui chart and its deployment configuration. Check how the chart exposes pod scheduling settings, then verify that nodeSelector and tolerations can be configured for the UI and are rendered into the resulting Kubernetes resources.
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
- 42/100