Temporal Server
Platform:
| Channel | Revision | Published | Runs on |
|---|---|---|---|
| latest/stable | 43 | 28 Jan 2025 | |
| latest/edge | 52 | 08 Aug 2025 | |
| 1.23/stable | 60 | 30 Apr 2026 | |
| 1.23/stable | 68 | 30 Apr 2026 | |
| 1.23/edge | 68 | 29 Apr 2026 | |
| 1.23/edge | 60 | 09 Dec 2025 |
juju deploy temporal-k8s --channel 1.23/stable
Cleanup and Extra Info
This is part of the Charmed Temporal Tutorial. Please refer to this page for more information and the overview of the content.
In this tutorial we’ve successfully deployed the Temporal Server, Temporal Admin, Temporal Web UI, and Temporal Worker, relating them together and running a basic workflow. You may now keep your Charmed Temporal K8s deployment running and write more complex workflows, or clean up your environment as shown below.
Remove and Cleanup Environment
If you’re done with testing and would like to free up resources on your machine, just run the following command:
juju destroy-controller -y --destroy-all-models --destroy-storage temporal-controller
Warning: when you remove the models as shown, you will lose all the data in PostgreSQL and any other applications inside the model!
If you followed the cross-model deployment path and created a separate temporal-workers-model, the --destroy-all-models flag above tears down both models on the controller in one go. No additional cleanup is needed.
Next Steps
If you’re looking for what to do next you can:
-
Configure the Temporal worker for production:
auth-secret-id, environment variables, Vault, TLS, Sentry, and the PostgreSQL relation. -
Upgrade an existing deployment from
latest/stableto1.23/stable. -
Explore Temporal scalability and observability.
-
Explore workflow samples.
-
Report any problems you encountered for any of the following charms: