Configuration and deployment user guides

Camunda 8 Self-Managed is highly customizable and can be deployed in different setups. This section highlights various use cases and scenarios of configuring Camunda 8 beyond the default values.

Each guide is considered complete and a standalone use case. However, view the deploying Camunda 8 using Helm charts page, as this is the base for all guides.

Accessing components without Ingress

Accessing Camunda 8 components externally without Ingress

Combined and separated Ingress setup

Camunda 8 Self-Managed combined and separated Ingress setup

Using existing Elasticsearch

Learn how to use an existing Elasticsearch instance in Camunda 8 Self-Managed Helm chart deployment.

Using Amazon OpenSearch Service

Learn how to use an Amazon OpenSearch Service instance in Camunda 8 Self-Managed deployment.

Use existing PostgreSQL

Learn how to use an Amazon OpenSearch Service instance in Camunda 8 Self-Managed deployment.

Configure custom headers

Learn how to configure DB client custom headers

Custom manifests

Learn how to add extra Kubernetes manifests to Helm deployments by defining them in the values.yaml file.

Installing in an air-gapped environment

Camunda 8 Self-Managed installation in an air-gapped environment

Running custom Connectors

Run custom Connectors in your Helm Kubernetes cluster.

Prefix Elasticsearch indices

Configure Elasticsearch index prefixes to structure your data, and ensure data isolation.

Multi-namespace deployment

Deploy Camunda 8 Self-Managed across several namespaces for better resource management and environment separation.

Verifying Camunda 8 installation with a demo app

Ensure your installation is functioning properly by learning how to install the payment example process application on Camunda 8 Self-Managed.

Managing secrets in Helm charts

Provides an overview for configuring and managing secrets when using the official Helm chart.