Temporal Server
| Channel | Revision | Published | Runs on |
|---|---|---|---|
| latest/stable | 43 | 28 Jan 2025 | |
| latest/edge | 52 | 08 Aug 2025 | |
| 1.23/edge | 59 | 08 Oct 2025 |
juju deploy temporal-k8s
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:
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
Check status:
juju status
Wait until the application is ready - when it is ready, juju status will show:
Model Controller Cloud/Region Version SLA Timestamp
temporal-model temporal-controller ck8s 3.6.9 unsupported 22:36:50Z
App Version Status Scale Charm Channel Rev Address Exposed Message
postgresql-k8s 14.15 active 1 postgresql-k8s 14/stable 495 10.152.183.200 no
temporal-admin-k8s blocked 1 temporal-admin-k8s latest/stable 13 10.152.183.97 no admin:temporal relation: database connections info not available
temporal-k8s blocked 1 temporal-k8s latest/stable 43 10.152.183.120 no admin:temporal relation: schema is not ready
Unit Workload Agent Address Ports Message
postgresql-k8s/0* active idle 10.1.0.36 Primary
temporal-admin-k8s/0* blocked idle 10.1.0.168 admin:temporal relation: database connections info not available
temporal-k8s/0* blocked idle 10.1.0.152 admin:temporal relation: schema is not ready
Relate Admin to Server
Relate the admin interface:
juju relate temporal-k8s:admin temporal-admin-k8s:admin
Monitor relations until they settle:
juju status --relations
After a short while, all applications should be active:
Model Controller Cloud/Region Version SLA Timestamp
temporal-model temporal-controller ck8s 3.6.9 unsupported 22:37:09Z
App Version Status Scale Charm Channel Rev Address Exposed Message
postgresql-k8s 14.15 active 1 postgresql-k8s 14/stable 495 10.152.183.200 no
temporal-admin-k8s 1.23.1 active 1 temporal-admin-k8s latest/stable 13 10.152.183.97 no
temporal-k8s active 1 temporal-k8s latest/stable 43 10.152.183.120 no
Unit Workload Agent Address Ports Message
postgresql-k8s/0* active idle 10.1.0.36 Primary
temporal-admin-k8s/0* active idle 10.1.0.168
temporal-k8s/0* active idle 10.1.0.152
Integration provider Requirer Interface Type Message
postgresql-k8s:database temporal-k8s:db postgresql_client regular
postgresql-k8s:database temporal-k8s:visibility postgresql_client regular
postgresql-k8s:database-peers postgresql-k8s:database-peers postgresql_peers peer
postgresql-k8s:restart postgresql-k8s:restart rolling_op peer
postgresql-k8s:upgrade postgresql-k8s:upgrade upgrade peer
temporal-admin-k8s:admin temporal-k8s:admin temporal regular
temporal-admin-k8s:peer temporal-admin-k8s:peer temporal-admin peer
temporal-k8s:peer temporal-k8s:peer temporal peer
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 only works for Charmed Temporal version 1.23/stable or later.
See next: Deploy Temporal Web UI