zalando / zalando/postgres-operator
Question: Is it possible to use pgbouncer-exporter with pooler?
Open
Nobody has claimed this yet.
question
- 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.1
- Kubernetes [Bare Metal K8s]
- Are you running Postgres Operator in production? [yes]
- Type of issue? [question]
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 clarifying how pgbouncer-exporter is expected to interact with the PostgreSQL Operator's pooler in the Kubernetes bare-metal setup described. Check the referenced postgres-operator v1.10.1 behavior and the single existing comment, then determine whether compatibility is already supported or would require a defined feature; the issue does not name files, tests, or a concrete completion condition.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes, postgresql
- Domain
- databases, devops, observability
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100