• Which image of the operator are you using?
  • ghcr.io/zalando/postgres-operator:v1.14.0
• **Where do you run it? Is it cloud or metal?
  • Kubernetes / Azure AKS 1.33.1
• Are you running Postgres Operator in production?
  • yes
• Type of issue?
  • question/feature request

We want to split read (secondary) and write (primary) requests of our app to the postgres db . The split will be done on the application level. Theoretically, this should be easy as the operator already creates the "ourinstance-postgres-db" & "ourinstance-postgres-db-repl" services.

The problem i see is that we have the connection pooler / pgbouncer configured via the operator, which only configures the primary postgres service host "ourinstance-postgres-db" in the pgbouncer.ini. As our read request should be pooled too I wonder how that can be configured at the moment?

Is there already a way to add "ourinstance-postgres-db-repl" to the pooler, via the operator config?

At the moment I only see the option to configure another pg_bouncer outside the operator. Is this correct?

If yes, I really would love to see this configurable through the operator too.