Skip to main content
This guide is for infrastructure teams operating a Kubernetes deployment. For deployment models, see SaaS and BYOC.
The Midaz chart deploys Ledger by default and enables its Valkey, PostgreSQL, MongoDB, and RabbitMQ dependencies by default. CRM is optional and disabled by default.
Use the Ledger workload for new installations. The chart does not deploy separate onboarding or transaction workloads.
The OpenTelemetry Collector is a separate chart. The Midaz chart can inject OTEL connection variables into Ledger, CRM, and Tracer, but it does not install a collector.

​
Prerequisites

  • A Kubernetes cluster compatible with the chart and ingress controller you use.
  • Helm 3 installed locally.
  • kubectl installed and configured with access to the cluster.
  • Access to the registry that serves the selected chart and images.
  • DNS and TLS material if you configure ingress.

​
Install Midaz

Create a values.yaml that supplies the chart’s required credentials before installing. When you use bundled RabbitMQ, follow the dependency configuration.

​
Verify the installation

Check the Helm release and the workloads created in the namespace:
If a workload is not ready, inspect its events and logs:
The exact workload count depends on the values you use, including whether bundled dependencies and optional CRM are enabled.

​
Next steps