Release notes v2.4.0
Release highlights
- Version name: ClusterControl 2.4.0
- State: Latest (long-term support)
- First release date: March 9th, 2026
- Maintenance status: Active
- Total maintenance builds: 1
- Last release date: N/A
- PostgreSQL new user management GUI
- Prometheus monitoring endpoints are secured with basic authentication and TLS encryption by default, protecting metrics data in transit.
- Faster cluster info retrieval through a new caching layer. Users managing large numbers of clusters should notice faster page loads and API responses.
- CMON controller pool for ClusterControl scalability
- HAProxy node discovery now uses internal hostnames by default, reducing false alarms and improving reliability in environments where database nodes are registered by internal or data hostnames.
- Improved Kubernetes secret handling reliability.
- ClusterControl now automatically downloads, verifies, and refreshes expired MongoDB GPG keys, including support for MongoDB Enterprise. This prevents deployment and maintenance failures caused by expired signing keys.
- Drop support for new cluster deployments for MongoDB-related clusters 6.0 and older.
- CMON HA support is deprecated, in favour of CMON controller pool.
- CMON Controller Pool does not support HA setup yet. This will be included in the upcoming release.
- Follow standard upgrade procedures as outlined in the documentation.
Maintenance Release: March 24th, 2026
-
Build:
- clustercontrol-controller-2.4.0-18342
- clustercontrol-mcc-2.4.0-774
- clustercontrol2-2.4.0-2231
- clustercontrol-controller-2.3.4-18341
- clustercontrol-mcc-2.3.4-775
- clustercontrol2-2.3.4-2232
-
Controller:
-
Bugfixes:
- Fixed an issue where the
outgoing_messagestable could fill up unnecessarily in CCX deployments. (CLUS-7145) - Prevented automatic database schema upgrades in CCX environments to avoid unintended side effects. (CLUS-7158)
- Cluster migration no longer aborts when a cluster has no SSL certificate files under
/var/lib/cmon/ca. (CLUS-7112) - Fixed missing adapter checks in secure file handling that could cause incorrect results when checking for the existence of configuration files. (CLUS-7163)
- Exceptions thrown during Kubernetes configuration checks and job execution are now properly caught and handled, preventing unexpected crashes. (CLUS-7164)
- Fixed a regression that prevented editing of MySQL database users. (CLUS-7071)
- Fixed PgBouncer deployment failures when PostgreSQL nodes are running on a non-default port. (CLUS-6998)
- Fixed Cluster Load metric options on the Overview Page appearing clickable but having no effect. (CLUS-6975)
- Fixed the “Rows per Page” control in the ProxySQL UI not correctly updating the number of displayed rows. (CLUS-6973)
- Sorting by “Hits” in the ProxySQL Rules view now sorts numerically instead of alphabetically, ensuring accurate ordering. (CLUS-6974)
- Fixed an issue where login was attempted before the Kubernetes operator ping completed, causing intermittent login failures. (CLUS-6764)
- Fixed an extra space in the connection pool example string that could cause unexpected issues. (CLUS-7083)
- Fixed an issue where the
-
Improvements
- PostgreSQL Backup Reliability - Updated
pg_basebackupto use the stream WAL method for more reliable base backups. (CLUS-7172) - Kubernetes Secret Migration - ClusterControl now automatically migrates cluster configuration files to Kubernetes Secrets before the daemon starts, improving security posture in Kubernetes environments. (CLUS-7171)
- Monitoring Exporter Updates - Several monitoring exporters have been updated to newer versions for improved compatibility and observability. (CLUS-7080)
- User Management - The “Disable Login” button has been renamed to “Disable User” for clarity, and user locking (login/nologin) is now supported. (CLUS-6712)
- Audit Logging - Audit logging has been added to user management, along with general improvements to the user details view. (CLUS-6713)
- Controller Retry - A retry option is now available in the Add Controller job action menu, making it easier to recover from failed controller additions. (CLUS-7044)
- File migration events are now logged at INFO level instead of WARNING, reducing noise in operational logs. (CLUS-7112)
- Redis/Valkey and MSSQL log files are now included in Error Reports for more complete diagnostics. (CLUS-7007)
- PostgreSQL Backup Reliability - Updated
-
-
GUI:
- Long cluster names are now displayed in full in the left-side navigation menu. (CLUS-7078)
- Long SQL queries in the ProxySQL UI now wrap automatically, making them easier to read without horizontal scrolling. (CLUS-6976)
- Granular controller access with CIDR /32 - You can now use a /32 CIDR mask to restrict access to a specific controller IP address. A helpful tooltip has been added to guide you through this setting. (CLUS-7018)
Initial Release: March 9th, 2026
- Build:
- clustercontrol-controller-2.4.0-18159
- clustercontrol-mcc-2.4.0-759
- clustercontrol2-2.4.0-2223
- clustercontrol-controller-2.3.4-18160
- clustercontrol-mcc-2.3.4-760
- custercontrol2-2.3.4-2224
- s9s-tools 1.9.2026021709
We’re pleased to announce the release of ClusterControl v2.4.0 LTS which adds support for:
Scaling ClusterControl with CMON Controller Pool - GA Release
Scalable pool of controllers, designed for demanding, multi‑site and high‑growth environments. This work improves scalability, resilience, and day‑2 operations when managing many clusters.
- Activate/Deactivate CMON Controller Pool on an existing controller, enabling gradual adoption and rollback
- Horizontal Scaling: Automatically add and remove controllers
- Shared CMON configurations using NFS
- Integrated UI/UX when enabling CMON Controller Pool
- HA setup is currently not available - will be included in the upcoming release.
PostgreSQL DB User Management (v2)
We’re continuing to enhance PostgreSQL user management in ClusterControl to make day‑to‑day operations simpler and safer.
- Improvements to user creation, role assignment, and permission management
-
Create, edit, and assign PostgreSQL roles directly from ClusterControl
- This helps standardize access patterns across databases and reduces manual psql work
-
View and edit database, schema, and table‑level permissions
- This will provide a clearer overview of who can access what, and simplify adjustments to fine‑grained permissions
-
Manage PostgreSQL authentication methods and password policies
- Enforce security standards for database users at scale
-
Improved support for automatic client authentication (
pg_hba.conf) changes and synchronization when new users are created.- Reduces configuration drift and lowers the risk of connectivity issues after user creation
-
UI and UX refinements across the board - Make complex permission and user-management flows easier to understand and operate.