Skip to main content
Lerian publishes Helm charts for Midaz and supporting services. Deploy each chart independently and review its Chart.yaml and values before choosing a version.

​
Midaz dependencies

The midaz-helm chart can deploy these dependencies by default:
  • Valkey
  • PostgreSQL
  • MongoDB
  • RabbitMQ
For production, you can disable a bundled dependency and configure the Ledger to use an externally managed service. See Configuring dependencies.

​
OpenTelemetry Collector

The OpenTelemetry Collector is a separate chart. It is no longer a dependency of midaz-helm. Install it separately when you use the Midaz chart’s default telemetry integration. The chart reads the export API key from a Secret named otel-api-key, key api-key, in the release namespace. Create that Secret before you install the chart:
Do not set opentelemetry-collector.extraEnvs in your own values to add the key. Helm replaces that list instead of merging it. The chart’s own entries, the API key and the node name that the kubelet receiver reads, disappear with it.
The Midaz chart enables otel-collector-lerian.enabled by default. That setting injects OTEL environment variables into the Ledger, CRM, and Tracer deployments. It does not install a collector. The default endpoint is $(HOST_IP):4317.
If you use your own collector endpoint, disable that integration and configure the relevant OTEL variables in the service configuration.

​
Other charts

The Helm repository also contains charts for products such as Tracer. Their application and chart versions are independent from midaz-helm. Inspect the chart you deploy instead of assuming a shared version.

​
Resources