We strongly recommend using Kubernetes and Helm to deploy and run Camunda 8 in production.
There are many ways you can provision and configure a Kubernetes cluster, and there are a number of architectural choices you need to make. Will your workers run in the Kubernetes cluster or external to it? You will need to configure your Kubernetes cluster and modify this to suit the architecture you are building.
You can install Camunda 8 on your Kubernetes environment of choice, e.g.:
- Stock Kubernetes.
- Kubernetes KIND, Minikube, K3s, and MicroK8s for local development.
- Red Hat OpenShift, an enterprise ready solution with a focus on security.
- Cloud service providers like Google GKE, Azure AKS, Amazon EKS, etc.
Officially supported platforms
With the right configuration, Camunda 8 can be deployed on any Kubernetes distribution (Cloud or on-premise). However, we officially test and support a specific list of platforms.
Use Helm to install on Kubernetes
There are several alternatives to deploy applications to a Kubernetes cluster, but we recommend to use our provided Helm charts to deploy a set of components into your cluster. Helm allows you to choose exactly what chart (set of components) you want to install and how these components need to be configured.
At helm.camunda.io, you'll find a Helm chart to configure a three-broker cluster with two Elasticsearch instances, Operate, two Zeebe Gateways and Tasklist. This size is comparable with the Production-S cluster plan in Camunda 8 SaaS. It should be sufficient for 80% of use cases.
Refer to the documentation on Camunda's Helm charts for details.
To do, you must have the following tools installed in your local environment:
kubectl: Kubernetes Control CLI tool, installed and connected to your cluster
helm: Kubernetes Helm CLI tool