| Channel | Revision | Published | Runs on |
|---|---|---|---|
| 1/stable | 562 | Yesterday | |
| 1/stable | 563 | Yesterday | |
| 1/candidate | 562 | 16 Jun 2026 | |
| 1/candidate | 563 | 16 Jun 2026 | |
| 1/beta | 562 | 16 Jun 2026 | |
| 1/beta | 563 | 16 Jun 2026 | |
| 1/edge | 565 | Yesterday | |
| 1/edge | 564 | Yesterday |
juju deploy pgbouncer-k8s --channel 1/stable --trustClean up and extra info
This is part of the PgBouncer K8s Tutorial. Please refer to this page for more information and the overview of the content.
Remove and clean up environment
If you’re done with testing and would like to free up resources on your machine, just remove Multipass VM.
Warning: when you remove VM as shown below, you will lose all the data in PostgreSQL and any other applications inside Multipass VM!
For more information, see multipass delete.
multipass delete --purge my-vm
Next Steps
In this tutorial, we’ve successfully deployed PgBouncer, added/removed cluster members, added/removed users to/from the database, and even enabled and disabled TLS. You may now keep your deployment running and write to the database, or remove it entirely.
If you’re looking for what to do next, you can:
- Run Charmed PostgreSQL VM on LXD.
- Check out our Charmed offerings of MySQL K8s and Kafka K8s.
- Read about High Availability Best Practices
- Report any problems you encountered.
- Give us your feedback.
- Contribute to the code base