
PgBouncer
- Canonical
- Databases
Channel | Revision | Published | Runs on |
---|---|---|---|
latest/stable | 5 | 17 Jan 2022 | |
1/stable | 642 | 04 Feb 2025 | |
1/stable | 641 | 04 Feb 2025 | |
1/stable | 640 | 04 Feb 2025 | |
1/stable | 639 | 04 Feb 2025 | |
1/candidate | 642 | 29 Jan 2025 | |
1/candidate | 641 | 29 Jan 2025 | |
1/candidate | 640 | 29 Jan 2025 | |
1/candidate | 639 | 29 Jan 2025 | |
1/beta | 642 | 29 Jan 2025 | |
1/beta | 641 | 29 Jan 2025 | |
1/beta | 640 | 29 Jan 2025 | |
1/beta | 639 | 29 Jan 2025 | |
1/edge | 658 | Yesterday | |
1/edge | 657 | Yesterday | |
1/edge | 656 | Yesterday | |
1/edge | 655 | Yesterday |
juju deploy pgbouncer --channel 1/stable
Deploy universal operators easily with Juju, the Universal Operator Lifecycle Manager.
Platform:
22.04
20.04
18.04
16.04
How to enable encryption
PgBouncer is a subordinate charm. When integrated to a host application (principal charm), it serves on localhost, so TLS encryption is not necessary.
If you are using data-integrator
, PgBouncer will open a port to listen to TCP traffic. In this case, because PgBouncer is exposed, TLS encryption is recommended.
Enable TLS
First, deploy the TLS charm:
juju deploy self-signed-certificates --config ca-common-name="Tutorial CA"
To enable TLS, integrate the two applications:
juju integrate self-signed-certificates pgbouncer
To enable TLS on PostgreSQL, refer to Charmed PostgreSQL | How to enable security.