crm.enabled workload and the plugin-fees-helm chart for older application releases. These are legacy compatibility surfaces, not the Midaz v4 deployment model.
Production recommendation
We do not recommend using the Midaz Helm chart’s default dependencies (databases, cache, and message broker) in production environments. For production-grade deployments, follow our best practices to operate these dependencies with proper security, observability, backups, disaster recovery, and SLOs.
Best practices
Upgrade order
Always upgrade in this order:- Infrastructure (if needed)
- Midaz Core
- Plugins (one at a time)
Test first
Always test upgrades in a staging environment that mirrors production before applying to production.Monitor closely
Monitor logs and metrics closely for the first 15-30 minutes after an upgrade.Keep backups
Maintain backups of your Helm values and database before major upgrades.Upgrade checklist summary
Post-upgrade verification
1. Check pod status
Running and READY.
2. Verify services
3. Check the logs
On charts before v7.0.0 you also had
midaz-onboarding and midaz-transaction Deployments. Those services were removed in v7.0.0. On any current chart those names return NotFound.