Temporal Server
Platform:
| Channel | Revision | Published | Runs on |
|---|---|---|---|
| 1.23/stable | 96 | Yesterday | |
| 1.23/stable | 60 | 30 Apr 2026 | |
| 1.23/edge | 96 | Yesterday | |
| 1.23/edge | 60 | 09 Dec 2025 | |
| 1.31/stable | 95 | Yesterday | |
| 1.31/edge | 95 | Yesterday | |
| 1.31/edge | 75 | 04 Aug 2026 | |
| 1.30/edge | 90 | 16 Oct 2026 | |
| 1.29/edge | 88 | 16 Oct 2026 | |
| 1.28/edge | 87 | 16 Oct 2026 | |
| 1.27/edge | 86 | 16 Oct 2026 | |
| 1.26/edge | 83 | 15 Oct 2026 | |
| 1.25/edge | 91 | 16 Oct 2026 | |
| 1.24/edge | 84 | 16 Oct 2026 |
juju deploy temporal-k8s --channel 1.23/stable
Deploy Temporal Admin
This is part of the Charmed Temporal Tutorial. Please refer to this page for more information and the overview of the content.
The Temporal Admin Tools are a set of command-line utilities used to configure and support the Temporal server.
Requirements
- You have completed Environment Setup.
- You have completed Deploy Temporal Server.
- You have completed Deploy PostgreSQL Database.
Deploy
To deploy Charmed Temporal Admin, you need to run the following command, which will fetch the charm from Charmhub and deploy it to your model:
juju deploy temporal-admin-k8s --channel 1.31/stable --base ubuntu@26.04
Check status:
juju status
Wait until the application is ready, when it is ready, juju status will show admin:temporal relation: database connections info not available at the admin app and admin:temporal relation: schema is not ready on the server app.
Relate Admin to Server
The admin charm in 1.31/stable requires two relations to reach active:
admin- schema management bridge between admin and server.temporal-host-info- supplies the Temporal frontend’s gRPC host and port to the admin charm so that itscliaction can reach the server.
Add both:
juju integrate temporal-k8s:admin temporal-admin-k8s:admin
juju integrate temporal-k8s:temporal-host-info temporal-admin-k8s:temporal-host-info
Deprecation notice:
server-nameis removed. Thetemporal-host-inforelation must be used.
Monitor relations until they settle:
juju status --relations
After a short while, all applications should be active.
Create the initial namespace
You can run the following command to create the initial Temporal namespace:
# Create default namespace:
juju run temporal-admin-k8s/0 cli args="operator namespace create --namespace default --retention 3d" --wait 1m
# Output:
Running operation 19 with 1 task
- task 20 on unit-temporal-admin-k8s-0
Waiting for task 20...
output: |
Namespace default successfully registered.
result: command succeeded
The command above uses the cli action with the modern temporal CLI grammar. In 1.23/stable, the legacy tctl action was renamed to cli and the underlying binary changed from the older tctl to the newer temporal CLI. Operator scripts that previously called juju run temporal-admin-k8s/0 tctl args="..." (with the old grammar like --namespace X namespace register --retention 72h) must be updated.
If you are upgrading an existing deployment, see the latest/stable → 1.23/stable upgrade guide.
See next: Deploy Temporal Web UI