PgBouncer connection endpoints now resolve correctly in Percona PostgreSQL

Percona PostgreSQL clusters now publish the correct connection address for PgBouncer in both deployment shapes: the load balancer address when PgBouncer is exposed through one, and the direct database host when PgBouncer runs without replicas.

Previously, clients could receive a wrong or unreachable endpoint in these configurations and fail to connect until the address was corrected manually.

The fix is available now with provider-percona-postgresql v0.5.0. To learn more, visit the release notes.