Please vote on this issue by adding a :thumbsup: reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment
Tell us about the feature
Right now the setup that we have is the following:
pgBouncer (connection pooler) points to Primary node of the cluster
all reads and writes go to one node
we also have replicas Kubernetes Service that points to Replica nodes of the cluster, but these connections are not pooled
The problem here, is that users cannot leverage scaling capabilities of PostgreSQL cluster on Kubernetes in full, cause connections to replicas are not pooled.
We need to come up with the design and implement it, that is going to provide easy failover and scalability for PostgreSQL on Kubernetes.
[~hamid.akhtar] is researching the approach that we are using on non-Kubernetes environments.
Community Note
Tell us about the feature
Right now the setup that we have is the following:
pgBouncer (connection pooler) points to Primary node of the cluster
we also have replicas Kubernetes Service that points to Replica nodes of the cluster, but these connections are not pooled
The problem here, is that users cannot leverage scaling capabilities of PostgreSQL cluster on Kubernetes in full, cause connections to replicas are not pooled.
We need to come up with the design and implement it, that is going to provide easy failover and scalability for PostgreSQL on Kubernetes.
[~hamid.akhtar] is researching the approach that we are using on non-Kubernetes environments.
Link to JIRA