zalando / zalando/postgres-operator

Feature Request: Connection Pooler Sidecar

Open
#1,153 4 comments 17 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement good first issue
Dominant language
Go
Stars
5.2k
Forks
1.1k
Avg merge
2d 16h
Merged PRs (30d)
3

Description

Hello

I would like to have pgbouncer-exporter as a sidecar for the connection pooler.
I don't think it's possible right now.

It would be great to have the same options for sidecars as in the cluster.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No file, test, or entry point is identified in the issue. Start by locating how cluster sidecars and their options are configured, then determine how the connection pooler and pgbouncer-exporter are represented. Done means the pooler sidecar supports the same options available to cluster sidecars, with coverage for the requested behavior.

Written by the indexing model from the issue text.

Assessment

Tech stack
kubernetes, postgresql
Domain
databases, infrastructure
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.