zalando / zalando/postgres-operator
NodeAffinity settings doesn't create affinity rules
Open
Nobody has claimed this yet.
bug
- Dominant language
- Go
- Stars
- 5.2k
- Forks
- 1.1k
- Avg merge
- 2d 16h
- Merged PRs (30d)
- 3
Description
Hi,
NodeAffinity settings doesn't create affinity rules for connection pooler. Only operator and acid-postgres receive affinity.
What is the desired setup to use for affinity rules on connection pooler? (I'm using Helm values)
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 reproducing the issue with the reported Helm values and compare affinity handling for the operator, acid-postgres, and connection pooler. Trace the connection pooler configuration entry point and determine the desired affinity setup. Done means connection pooler affinity rules are created consistently with the expected configuration, with coverage for the observed behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- helm, kubernetes, postgresql
- Domain
- databases, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100