zalando / zalando/postgres-operator
question: postgres instance & connection pooler instance scheduling
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 5.2k
- Forks
- 1.1k
- Avg merge
- 2d 16h
- Merged PRs (30d)
- 3
Description
Currently the way I see it they both share node affinity / anti affinity / tolerations
I wanted to make sure that when scheduling and executing poolers would be on dedicated pooler nodes, postgres instances would be on dedicated postgres nodes & anti affinity would take care of cross-zone HA
is there something I'm missing in the docs that allows me to do that or its currently not possible?
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
No files, tests, or entry points are mentioned. Start by reviewing the operator's scheduling documentation and configuration options for PostgreSQL instances and poolers; done means documenting whether separate nodes and cross-zone anti-affinity can be configured, or clearly stating that they cannot.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes, postgresql
- Domain
- databases, devops, infrastructure
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100