Blogs›Temporal›Temporal Server Deployment Automation

Temporal Server Deployment Automation

posts

2022–2026

The Helm Charts for deploying the Temporal Service to Kubernetes have reached version 1.0.0, signifying a point of stability. This release removes bundled sub-charts for databases (Cassandra, PostgreSQL, MySQL) and optional components like Elasticsearch, Prometheus, and Grafana, requiring users to provide and configure these separately. The `values.yaml` structure has been updated, with changes to internal frontend configuration and `imagePullSecrets` format. New capabilities include configurable readiness probes, custom deployment strategies, `minReadySeconds` for rollout control, configurable log levels, and support for AWS IAM authentication and read-only filesystems for Temporal Docker images.

2026

An important milestone for Temporal’s Helm Charts

4/21/2026

The 1.0.0 release of Temporal's Helm Charts introduces several breaking changes and new capabilities. Breaking changes include the removal of bundled database and optional component sub-charts, requiring external provision and configuration. The `values.yaml` structure has been updated, with specific changes to `server.internal-frontend` and `imagePullSecrets` format. New capabilities include configurable readiness probes, custom deployment strategies, `minReadySeconds`, configurable log levels, and enhanced security features like AWS IAM authentication and read-only filesystems for Docker images.

2022

How Temporal Auto-Setup simplifies deployment

1/5/2022

This post details the `auto-setup.sh` script's role in Temporal Server deployment, covering Temporal schema setup (database and Elasticsearch), server setup including default namespace registration, and adding custom search attributes. It explains how these steps abstract away direct binary management and provides guidance for adapting Temporal to different infrastructure needs.