zalando / zalando/postgres-operator
Single ingress for database cluster
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 5.2k
- Forks
- 1.1k
- Avg merge
- 2d 16h
- Merged PRs (30d)
- 3
Description
Hi Everyone,
Currently, I see the option to add LB for master and replicas separately, I have a use case where I need to expose a single endpoint for both read/write operations and it would be great if you have a mechanism that sends Reads to Replicas and Writes to Master.
I don't think single LB for a cluster is available currently.
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 reviewing the operator's existing configuration for separate master and replica load balancers. Determine the entry points and tests governing cluster ingress and routing, then define acceptance checks for one endpoint that sends reads to replicas and writes to the master.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes, postgresql
- Domain
- databases, networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100