PgBouncer K8s
- Canonical
- Databases
| Channel | Revision | Published | Runs on |
|---|---|---|---|
| 1/stable | 269 | 11 Sep 2024 | |
| 1/stable | 268 | 11 Sep 2024 | |
| 1/candidate | 360 | Today | |
| 1/candidate | 359 | Today | |
| 1/beta | 360 | 16 Dec 2024 | |
| 1/beta | 359 | 16 Dec 2024 | |
| 1/edge | 360 | 04 Dec 2024 | |
| 1/edge | 359 | 04 Dec 2024 |
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:
Charm Statuses
WARNING : it is an work-in-progress article. Do NOT use it in production! Contact Canonical Data Platform team if you are interested in the topic.
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 |