PgBouncer K8s
- Canonical
- Databases
Channel | Revision | Published | Runs on |
---|---|---|---|
1/stable | 269 | 11 Sep 2024 | |
1/stable | 268 | 11 Sep 2024 | |
1/candidate | 269 | 09 Sep 2024 | |
1/candidate | 268 | 09 Sep 2024 | |
1/beta | 269 | 09 Sep 2024 | |
1/beta | 268 | 09 Sep 2024 | |
1/edge | 348 | Yesterday | |
1/edge | 347 | Yesterday |
juju deploy pgbouncer-k8s --channel 1/edge
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:
Juju tech details
Juju is an open source orchestration engine for software operators that enables the deployment, integration and lifecycle management of applications at any scale, on any infrastructure using charms.
This charm is an operator - business logic encapsulated in reusable software packages that automate every aspect of an application’s life. Charms are shared via CharmHub.
See also:
Breaking changes between Juju 2.9.x and 3.x
As this charm documentation is written for Juju 3.x, users of 2.9.x will encounter noteworthy changes when following the instructions. This section explains those changes.
Breaking changes have been introduced in the Juju client between versions 2.9.x and 3.x. These are caused by the renaming and re-purposing of several commands - functionality and command options remain unchanged.
In the context of this guide, the pertinent changes are shown here:
2.9.x | 3.x |
---|---|
add-relation | integrate |
relate | integrate |
run | exec |
run-action --wait | run |
See the Juju 3.0 release notes for the comprehensive list of changes.
The response is to therefore substitute the documented command with the equivalent 2.9.x command. For example:
Juju 3.x:
juju integrate pgbouncer-k8s:database postgresql-test-app
juju run postgresql-k8s/leader get-password
Juju 2.9.x:
juju relate pgbouncer-k8s:database postgresql-test-app
juju run-action --wait postgresql-k8s/leader get-password