zalando / zalando/postgres-operator
Does the standby cluster initialization work when primary has pooler enabled?
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 5.2k
- Forks
- 1.1k
- Avg merge
- 2d 16h
- Merged PRs (30d)
- 3
Description
registry.opensource.zalan.do/acid/postgres-operator:v1.10.0
- Where do you run it - cloud or metal? Kubernetes or OpenShift? [Bare Metal K8s]
- Are you running Postgres Operator in production? [yes]
- Type of issue? [question]
When starting cluster pointing to primary with pooler enabled, the standby fails to initialize. In our typical bare metal (non K8) PostgreSQL installations, we typically run Postgres on port 5431 and pgbouncer on 5432. How can we do similar using the operator?
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
The issue names no source file, test, or entry point. Start by reproducing standby initialization with PostgreSQL Operator v1.10.0 on bare-metal Kubernetes, using PostgreSQL on port 5431 and the pooler on 5432; done means identifying whether this configuration is supported and documenting the required setup or limitation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes, postgresql
- Domain
- databases, devops
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100