We recommend you use Kubernetes when deploying Zeebe to production.
|Helm||Helm allows you to choose exactly what chart (set of components) you want to install and how these components need to be configured.|
|Zeebe Operator (experimental)||The objective of the Zeebe k8s Operator is to simplify and natively integrate Zeebe with k8s, to solve operational burden, and facilitate the creation and maintenance of a set of clusters.|
Zeebe broker nodes need to be deployed as a StatefulSet to preserve the identity of cluster nodes. StatefulSets require persistent storage, which must be allocated in advance. Depending on your cloud provider, the persistent storage differs as it is provider-specific.
In the zeebe-kubernetes repository, you'll find example Kubernetes manifests to configure a 3-broker cluster with the Elasticsearch exporter and the Operate preview. Examples are provided for provisioning storage on Google Cloud Platform, and Microsoft Azure.
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.
Zeebe gateway is deployed as a stateless service.
We support Kubernetes startup and liveness probes for Zeebe gateway.