Upcoming Architectural Changes to the Frappe/ERPNext Helm Chart

revant_one · October 17, 2025, 10:55am

There needs to be a major architectural update to the official Helm chart. Check this issue:

This update introduces new built-in components for the database and cache, replacing the default dependency on Bitnami subcharts.

What’s Changing?

New Default Backend: New installations will now use a built-in MariaDB StatefulSet and DragonflyDB for caching/queues by default. This simplifies the setup process significantly.
Deprecation of Subcharts: The classic Bitnami subcharts for MariaDB, PostgreSQL, and Redis will be deprecated.

How Does This Affect You?

For Existing Users: We have prioritized a seamless upgrade path. Your existing deployments using Bitnami subcharts will continue to work after running helm upgrade. You will simply see a deprecation notice.
For New Users: The default installation is now much simpler, with fewer external dependencies to manage.

For feedback, review and development follow PR:

github.com/frappe/helm

feat(chart): introduce built-in components and deprecate subcharts

main ← revant:feat-dragonflydb

opened 06:11AM - 15 Oct 25 UTC

revant

+833 -460

This commit introduces a major architectural change to the Helm chart, moving fr…om a dependency on Bitnami subcharts to self-contained, built-in components for the database and cache. This change simplifies the default installation, enhances maintainability, and provides a clear, modern path for new deployments. **Key Changes:** 1. **New Built-in Components**: * A built-in MariaDB StatefulSet (`mariadb-sts`) is now available and is the recommended database backend for new installations. * DragonflyDB is introduced as the new, high-performance default for caching (`dragonfly-cache`) and queues (`dragonfly-queue`), replacing Redis. * A built-in PostgreSQL StatefulSet (`postgresql-sts`) is also included for custom Frappe apps. 2. **Backward Compatibility and Seamless Upgrades**: * The classic Bitnami subcharts for MariaDB, PostgreSQL, and Redis are preserved for backward compatibility. * Aliases (e.g., `mariadb-subchart`) are introduced in `Chart.yaml` to manage these legacy dependencies cleanly. * The `worker.healthProbe` has been significantly improved with fallback logic to check for both new aliased service names and old service names, ensuring a seamless `helm upgrade` experience for existing users. 3. **Improved Configuration and Jobs**: * A new `externalRedis` section is added to `values.yaml` to provide a clear and functional way to configure external Redis instances. * All job templates (`configure`, `create-site`, `drop-site`) have been updated to correctly handle the full range of database and cache backends (built-in, subchart, and external). 4. **Documentation Overhaul**: * A new `MIGRATION.md` file has been added to provide a clear, step-by-step guide for users who wish to migrate from the legacy Bitnami subcharts to the new built-in components. * `README.md` has been significantly updated to reflect the new architecture, recommended installation commands, and configuration methods. * `NOTES.txt` now includes a prominent deprecation warning to inform users about the future removal of Bitnami subchart support. 6. **Testing**: * The test suite has been updated to validate the new recommended installation path using the built-in `mariadb-sts`, ensuring the primary path is robustly tested.