zalando / zalando/postgres-operator
Ability to run the master and replica load-balancers from the same host
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 5.2k
- Forks
- 1.1k
- Avg merge
- 2d 16h
- Merged PRs (30d)
- 3
Description
- Which image of the operator are you using? e.g. ghcr.io/zalando/postgres-operator:v1.14.0
- Where do you run it - cloud or metal? Kubernetes or OpenShift? local k3d cluster
- Are you running Postgres Operator in production? no
- Type of issue? feature request
The master and replica load balancers both use the same port number, preventing them from running on the same host. Please provide a way to change the port number being used by each load balancer so we can run them on the same host if needed. This is especially needed for debugging/testing against a local cluster.
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 where the operator creates the master and replica load balancers and assigns their ports. Check the local k3d setup described in the issue, then verify that each load balancer can be configured with a distinct port and both can run on one host.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes, postgresql
- Domain
- databases, infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100