| Channel | Revision | Published | Runs on |
|---|---|---|---|
| 1/stable | 520 | 02 Mar 2026 | |
| 1/stable | 519 | 02 Mar 2026 | |
| 1/candidate | 520 | 27 Feb 2026 | |
| 1/candidate | 519 | 27 Feb 2026 | |
| 1/beta | 520 | 27 Feb 2026 | |
| 1/beta | 519 | 27 Feb 2026 | |
| 1/edge | 525 | 05 Mar 2026 | |
| 1/edge | 524 | 05 Mar 2026 |
juju deploy pgbouncer-k8s --channel 1/stable --trust
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:
Charm Statuses
The charm follows standard Juju applications statuses. Here you can find the expected end-users reaction on different statuses:
| Juju Status | Message | Expectations | Actions |
|---|---|---|---|
| active | any | Normal charm operations | No actions required |
| waiting | any | Charm is waiting for relations to be finished | No actions required |
| maintenance | any | Charm is performing the internal maintenance (e.g. re-configuration) | No actions required |
| blocked | any | The manual user activity is required! | Follow the message hints (see below) |
| blocked | waiting for backend database relation to initialise | Normal behavior, charm needs all relations to work. | Follow the hint to establish a proper relation. |
| error | any | An unhanded internal error happened | Read the message hint. Execute juju resolve <error_unit/0> after addressing the root of the error state |
| terminated | any | The unit is gone and will be cleaned by Juju soon | No actions possible |
| unknown | any | Juju doesn’t know the charm app/unit status. Possible reason: K8s charm termination in progress. | Manual investigation required if status is permanent |