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
Architecture
The Charmed Temporal ecosystem consists of a number of different charmed operators related together. The diagram below shows a high-level illustration of the different charms and their relations. The charmed components are as follows:
-
Temporal Server: The Temporal server is a group of four independently scalable services (frontend, history, matching and worker). It is responsible for state management and task synchronization among other functionalities.
-
Temporal Admin: The Temporal Admin Tools are a set of command-line utilities used to configure and support the Temporal server.
-
Temporal UI: The Temporal Web UI is a user interface used to interact with and monitor Temporal workflows and activities.
-
PostgreSQL K8s: For Temporal persistence and visibility, we use the PostgreSQL K8s charmed operator. The PostgreSQL K8s charm can be deployed and related to the Temporal server.
-
Nginx Ingress Integrator: The Charmed Temporal K8s operator exposes its service ports using the Nginx Ingress Integrator charmed operator.
-
OpenFGA: The Charmed Temporal K8s operator can relate to the OpenFGA K8s charmed operator to enable an authorization layer and control namespace-level access.
-
S3 Integrator: The Charmed Temporal K8s operator can be used to enable event histories archival in an S3-compatible storage by relating it to the S3 Integrator charmed operator.
-
Temporal Worker: The Temporal Worker is the entity which listens and polls on specific task queue, and executes code in response to the task.
