
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:
Releases
This page provides high-level overviews of the dependencies and features that are supported by each revision in every stable release. To learn more about the different release tracks, see the Juju documentation about risk levels.
To see all releases and commits, check the Charmed PgBouncer K8s releases on GitHub.
Dependencies and supported features
For each release, this table shows:
- The PgBouncer version packaged inside
- The minimum Juju version required to reliably operate all features of the release
This charm still supports older versions of Juju 2.9. See the system requirements for more details
- Support for specific features
Revision | PgBouncer version | Juju version | TLS encryption | COS monitoring | Minor version upgrades |
---|---|---|---|---|---|
407, 408 | 1.21.0 |
3.6.1+ |
![]() |
![]() |
![]() |
359, 360 | 1.21.0 |
3.4.5+ |
![]() |
![]() |
![]() |
268, 269 | 1.21.0 |
3.4.5+ |
![]() |
![]() |
![]() |
228, 229 | 1.21.0 |
3.4.5+ |
![]() |
![]() |
|
144, 145 | 1.21.0 |
3.1.8+ |
![]() |
![]() |
|
103 | 1.21.0 |
3.1.7+ |
![]() |
![]() |
|
81 | 1.21.0 |
3.1.6+ |
![]() |
||
76 | 1.18.0 |
3.1.6+ |
![]() |
Architecture and base
Several revisions are released simultaneously for different bases/series using the same charm code. In other words, one release contains multiple revisions.
If you do not specify a revision on deploy time, Juju will automatically choose the revision that matches your base and architecture.
If you deploy a specific revision, you must make sure it matches your base and architecture via the tables below or with
juju info
.
Release 407, 408 (candidate
)
Older releases
Release 359, 360
Release 268, 269
Release 228, 229
Release 144,145
Release 103
Revision | amd64 |
arm64 |
Ubuntu 22.04 (jammy) |
---|---|---|---|
103 | ![]() |
![]() |
Release 81
Revision | amd64 |
arm64 |
Ubuntu 22.04 (jammy) |
---|---|---|---|
81 | ![]() |
![]() |
Release 76
Revision | amd64 |
arm64 |
Ubuntu 22.04 (jammy) |
---|---|---|---|
81 | ![]() |
![]() |
Note: Our release notes are an ongoing work in progress. If there is any additional information about releases that you would like to see or suggestions for other improvements, don’t hesitate to contact us on Matrix or leave a comment.