crm.enabled workload and the plugin-fees-helm chart for older application releases. These are legacy compatibility surfaces, not the Midaz v4 deployment model.
Rollback procedures
If something goes wrong after an upgrade, you can rollback to a previous version.
When to rollback
Consider rolling back if you observe:- Pods failing to start or crash-looping
- API errors or service unavailability
- Data inconsistencies
- Performance degradation
Check release history
View the revision history for a release:Execute rollback
Rollback to a specific revision:- Rollback Midaz to previous revision
- Rollback a plugin (example: Fees)
CRM has no release of its own to roll back. It ships inside the Midaz chart, so rolling back
midaz rolls CRM back with it.Verify rollback
- Verify release version
- Verify pods
- Check logs
- Current chart (v7.0.0+)
- Pre-v7.0.0 charts
Rollbacks may not revert database schema changes. If the upgrade included database migrations, you may need to restore from a database backup.
Troubleshooting
Pods stuck in Pending state
Symptom: Pods remain inPending status after upgrade.
Solution: Check for resource constraints:
- Describe pending pod
- Check node resources
Image pull errors
Symptom: Pods showImagePullBackOff or ErrImagePull.
Solution: Verify image registry access and credentials:
- Check pod events
- Verify image exists
Configuration errors
Symptom: Pods crash with configuration-related errors in logs. Solution: Compare your values with the new defaults:- View current values
- View chart defaults
Database connection issues
Symptom: Services fail to connect to PostgreSQL or MongoDB. Solution: Verify database connectivity and credentials:- Check database pods
- Check service logs
- Current chart (v7.0.0+)
- Pre-v7.0.0 charts
General rollback procedure
If you encounter issues after any upgrade:
Related resources
- Installing Midaz with Helm - Initial installation guide
- Midaz chart version compatibility - Current chart and application metadata
- Helm repository - Source code and release notes