temporal

Temporal is a distributed, scalable, durable, and highly available orchestration engine to execute asynchronous long-running business logic in a scalable and resilient way. The Temporal Helm chart automates deployment and configuration of Temporal in Kubernetes clusters using Minimus images.

Prerequisites

A subscription to the Minimus images included in the chart
A running Kubernetes cluster (v1.21 or higher is recommended)
kubectl installed and configured
Helm v3.8 or higher for OCI support (Installation instructions)
Cluster Admin privileges
A supported database backend (PostgreSQL, MySQL, or Cassandra) accessible from the cluster

Try It Out

In this example we will deploy Temporal on a Kubernetes cluster using the Minimus Temporal Helm chart. Temporal will provide a workflow orchestration engine with a web UI for monitoring and managing workflows.

Step 1: Start Cluster

If you have a cluster to work with, skip this step. Otherwise, start a Minikube cluster. Deployment instructions

Step 2: Create Namespace

Create a namespace:

kubectl create ns temporal

Step 3: Configure a Database

Temporal stores all workflow state in an external database and does not bundle one — the chart ships with no datastore configured, so it will not start until you point it at your own PostgreSQL, MySQL, or Cassandra instance. Provision a database reachable from the cluster, then describe it in a values.yaml:

temporal:
  server:
    config:
      persistence:
        defaultStore: default
        visibilityStore: visibility
        datastores:
          default:
            sql:
              pluginName: postgres12          # or mysql8; append _pgx for the pgx driver
              connectProtocol: tcp            # required — the server fails to start without it
              connectAddr: "postgresql.mydb.svc:5432"
              databaseName: temporal
              user: temporal
              password: "<password>"          # or omit and set existingSecret + secretKey
          visibility:
            sql:
              pluginName: postgres12
              connectProtocol: tcp
              connectAddr: "postgresql.mydb.svc:5432"
              databaseName: temporal_visibility
              user: temporal
              password: "<password>"

The chart runs schema setup for you (createDatabase and manageSchema default to true), so the temporal and temporal_visibility databases are created and migrated on first install. For Cassandra, Elasticsearch-backed visibility, TLS, and the full set of persistence options, see the upstream Temporal Helm chart.

Step 4: Deploy the Helm Chart

Deploy the Minimus Helm chart with your database configuration:

helm install my-temporal oci://helm.mini.dev/temporal \
  --version 1.6.0 \
  -f values.yaml \
  -n temporal \
  --wait

For the full list of tunables, see the Values tab.

Step 5: Verify Temporal is Running

Confirm the chart deployed successfully and Temporal started:

kubectl get pods -n temporal -l app.kubernetes.io/name=temporal

You should see output similar to:

NAME                                        READY   STATUS    RESTARTS   AGE
my-temporal-admintools-xxxxxxxxx-xxxxx      1/1     Running   0          2m
my-temporal-frontend-xxxxxxxxx-xxxxx        1/1     Running   0          2m
my-temporal-history-xxxxxxxxx-xxxxx         1/1     Running   0          2m
my-temporal-matching-xxxxxxxxx-xxxxx        1/1     Running   0          2m
my-temporal-web-xxxxxxxxx-xxxxx             1/1     Running   0          2m
my-temporal-worker-xxxxxxxxx-xxxxx          1/1     Running   0          2m

Step 6: Test HTTP Endpoint

Forward the Temporal web UI port to your local machine:

kubectl port-forward svc/my-temporal-web -n temporal 8080:8080

In a separate terminal, check the web UI is responding:

curl -sf http://localhost:8080/healthz

You can also open http://localhost:8080 in a browser to access the Temporal web UI for monitoring workflows and namespaces.

Step 7: Clean Up

Uninstall the chart and delete the namespace to remove all resources:

helm uninstall my-temporal -n temporal
kubectl delete namespace temporal

Terms & Info

Trademark

This catalog is published by Minimus. All product names, logos, and marks, other than those belonging to Minimus, shown are owned by their respective rights holders and appear here only to identify the open source software each image contains. Minimus claims no ownership of those marks and implies no affiliation with, endorsement by, certification by, or sponsorship by any rights holder.

Disclaimer

Images are provided "as-is" without warranty of any kind. "Hardened" refers to the security configuration applied at the time of build and does not constitute a guarantee of ongoing security or absence of vulnerabilities. The free tier is provided without support, SLA, or guaranteed patching timelines. Security updates may be applied to paid subscriptions before or instead of free tier images. By pulling or using any image you agree to our Terms of Use.