I'm wanting to deploy some sort of connection pooling within my applications across multiple nodes. Python naturally provides some pooling with the SQLAlchemy implementation; but obviously this probably does not scale as well as 1 central pool.

As far as I see it PGBouncer can Sit within each pod, it can be running as its own pod, or it can be running as a daemonset which ties a PGBouncer instance to be running for each kube node.

PGBouncer in container vs out

How would you / how have you deployed PGBouncer in a similar environment?

This question is equally relevant for twemproxy.

1 Answer 1


PGBouncer is a connection pooler. So, one instance of PGBouncer should be enough in between the apps and postgres.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.