Helm chart parameters

Helm chart parameters let you configure the components and behavior of your Camunda Self-Managed installation. The main way to customize these parameters is by using a values.yaml file.

In Helm charts, the values.yaml file defines configuration for your deployment. To tailor your installation to your needs, you can override parameters in this file or provide your own values file. It's best practice to keep the original values.yaml unchanged and maintain a separate file with your custom settings.

Templating support

Some values in values.yaml support Go template expressions (for example, {{ .Release.Name }}). Values that support templating are marked with "Supports templating" in their description in values.yaml. This includes podLabels, podAnnotations, and global.host, among others.

The following tables show the top-level configuration sections in values.yaml. Each section controls a specific area of the chart.

Global and orchestration cluster configuration

Section	Purpose
global	Configures shared settings that apply across components
orchestration	Configures orchestration cluster settings

For pod-level networking options such as dnsPolicy, dnsConfig, and orchestration.hostNetwork, see configure pod networking.

For service-level options such as the appProtocol hint per port, see configure Kubernetes Service ports.

Other Camunda applications

Section	Purpose
camundaHub	Configures Camunda Hub
connectors	Configures the Connector runtime
identity	Configures the Management Identity service
optimize	Configures the Optimize web application

External infrastructure

Camunda 8.10 no longer bundles infrastructure subcharts. Deploy PostgreSQL, Elasticsearch or OpenSearch, and Keycloak separately from the Camunda Helm chart. This lets you use your preferred deployment methods, leverage managed services, and manage infrastructure lifecycles independently of Camunda. See deploy required dependencies with Kubernetes operators.

note

Configure the secondary storage backend that fits your requirements. Depending on the component, topology, and version, you can use a document-store backend (Elasticsearch/OpenSearch) or an RDBMS-based secondary store.

See RDBMS configuration and the glossary entry RDBMS.

Migrating from Bitnami subcharts?

If you have an existing Camunda deployment using Bitnami subcharts, see the migration guide for step-by-step instructions and automated tooling to migrate your data to Kubernetes operators or managed services with minimal downtime.

Observability

Section	Purpose
prometheusServiceMonitor	Creates a Prometheus ServiceMonitor resource for metrics

Where to find all chart parameters

For a full list of supported Helm chart parameters, including default values and descriptions, see Helm chart parameters on Artifact Hub.

Check this page when installing or upgrading to ensure you use the latest options for your chart version.

Provided values files

In addition to the default values.yaml, the Helm chart repository includes several additional values files for special use cases.
You can use these files individually or combine them with your own overrides.

File	Purpose
values.yaml	The default configuration. Includes all chart parameters with baseline values.
values-local.yaml	Optimized for local development (for example, kind or Minikube). Adjusts resource requests and limits for smaller environments.
values-tls.yaml	An overlay that enables TLS for the connections the chart can configure. Requires a CA bundle secret in the namespace.
values-latest.yaml	Tracks the latest versions of the applications. This may include breaking changes and is intended for early testing.
values-digest.yaml	Uses the latest snapshot images referenced by digest (for internal development only).

Creating your own values files

To customize parameters, create an override file (for example, my-overrides.yaml) with custom settings.
This approach is recommended over editing values.yaml directly.

You can validate the keys in your overrides with the Camunda Helm Toolkit. This checks the supplied configuration, not the completeness or deployment readiness of all merged Helm values.

Combining multiple values files

Helm lets you specify multiple values files. You can layer them to build the configuration you need:

helm install camunda camunda/camunda-platform \
  -f values.yaml \
  -f values-local.yaml \
  -f my-overrides.yaml

If the same parameter is defined in more than one file, the value in the last file listed takes precedence. In the example above, settings from my-overrides.yaml override values from both values-local.yaml and values.yaml.