
PgBouncer K8s
- Canonical
- Databases
Channel | Revision | Published | Runs on |
---|---|---|---|
1/stable | 408 | 18 Feb 2025 | |
1/stable | 407 | 18 Feb 2025 | |
1/candidate | 408 | 14 Feb 2025 | |
1/candidate | 407 | 14 Feb 2025 | |
1/beta | 408 | 07 Feb 2025 | |
1/beta | 407 | 07 Feb 2025 | |
1/edge | 420 | Today | |
1/edge | 419 | Today |
juju deploy pgbouncer-k8s --channel 1/stable
Deploy Kubernetes operators easily with Juju, the Universal Operator Lifecycle Manager. Need a Kubernetes cluster? Install MicroK8s to create a full CNCF-certified Kubernetes system in under 60 seconds.
Platform:
Upgrade
Currently, the charm supports PgBouncer major version 1 only. Therefore, in-place upgrades/rollbacks are not possible for major versions.
Note: Canonical is not planning to support in-place upgrades for major version change. The new PgBouncer K8s charm will have to be installed nearby, and the data will be copied from the old to the new installation. After announcing the next PostgreSQL + PgBouncer major version support, the appropriate documentation for data migration will be published.
For instructions on carrying out minor version upgrades, see the following guides:
- Minor upgrade, e.g. PgBouncer 1.18 → PgBouncer 1.19
(including charm revision bump 99 → 102). - Minor rollback, e.g. PgBouncer 1.19 → PgBouncer 1.18
(including charm revision return 102 → 99).