PgBouncer
- Canonical
- Databases
Channel | Revision | Published | Runs on |
---|---|---|---|
latest/stable | 5 | 17 Jan 2022 | |
1/stable | 397 | 11 Sep 2024 | |
1/stable | 396 | 11 Sep 2024 | |
1/stable | 395 | 11 Sep 2024 | |
1/stable | 394 | 11 Sep 2024 | |
1/candidate | 558 | 12 Dec 2024 | |
1/candidate | 557 | 12 Dec 2024 | |
1/candidate | 556 | 12 Dec 2024 | |
1/candidate | 555 | 12 Dec 2024 | |
1/beta | 558 | 05 Dec 2024 | |
1/beta | 557 | 05 Dec 2024 | |
1/beta | 556 | 05 Dec 2024 | |
1/beta | 555 | 05 Dec 2024 | |
1/edge | 622 | Today | |
1/edge | 621 | Today | |
1/edge | 620 | Today | |
1/edge | 619 | Today |
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.