Skip to content

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: 2
  • Last release date: N/A
  • 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.
  1. Follow standard upgrade procedures as outlined in the documentation.

New Release: May 4th, 2026

  • Build:
    • clustercontrol-mcp-1.0.0-5

We’re excited to announce the release of ClusterControl MCP, a new integration that lets you manage your database clusters in plain English, directly from Claude Desktop, Claude Code, OpenAI Codex, or any MCP-compatible AI client. No dashboards, no SQL, no API calls.

This release ships with 69 tools and 20 MCP resources/templates covering:

  • Cluster inventory, topology & health
  • Jobs, alarms & performance diagnosis
  • Backups, restores & backup schedules
  • Maintenance windows & database user management
  • ProxySQL, schema advisors, audit logs & configuration
  • CMON controller logs and collected host log files
  • Built-in dry-run safety for all write operations
  • Sensitive output handling - PII and SQL text hidden by default with opt-in flags
  • MCP task support for long-running operations

See Reference Manual 🡒 MCP Server and Tutorials 🡒 Managing Clusters using ClusterControl MCP.

Maintenance Release: April 27th, 2026

  • Build:
    • clustercontrol-controller-2.4.0-18992
    • clustercontrol-mcc-2.4.0-825
    • clustercontrol2-2.4.0-2264
    • clustercontrol-controller-2.3.4-18991
    • clustercontrol-mcc-2.3.4-824
    • clustercontrol2-2.4.0-2263

This release introduces first-class support for incremental PostgreSQL backups using pg_basebackup — including streaming directly to S3, point-in-time recovery from an incremental chain, and new WAL-summarization controls exposed end-to-end from the Backup Wizard through to the controller. Valkey (Sentinel and Sharded) now supports a "Promote Replica" action, matching the existing Redis workflow. The release also resolves a collection of customer-reported issues across PostgreSQL user management, certificate issuance, MySQL user creation, view-only permissions, and cluster-switching stability.

New Features

  • Incremental PostgreSQL backups with pg_basebackup (streaming to S3): End-to-end support for pg_basebackup --incremental, including the controls, wizard flow, and restore paths needed to use it in production:

    • Backup Wizard — pg_basebackupincr is now a selectable backup method for PostgreSQL 17+. The wizard warns if the selected host has WAL summarization disabled, and ensures summarize_wal=true is set on the target before submitting the backup. (CLUS-7196, CLUS-7212, CLUS-7223)
    • Configure WAL — the node-level "Configure WAL" action lets you turn summarize_wal ON or OFF and refreshes the node state immediately. (CLUS-7196, CLUS-7280)
    • Under the hood — incremental backups run via pg_basebackup --incremental, support the summarize_wal setting across the full workflow, and stream directly to S3 (removing the local-disk capacity requirement). (CLUS-6563, CLUS-7084, CLUS-7086, CLUS-7213)
    • Backup manifests are now uploaded separately from the tarball for both full and incremental pg_basebackup backups, enabling cleaner storage and retrieval. (CLUS-7195)
    • Restore an incremental backup chain — ClusterControl automatically retrieves the full chain, reconstructs it with pg_combinebackup, and restores the combined data. (CLUS-7085, CLUS-7218, CLUS-7220, CLUS-7221)
    • Point-in-time recovery (PITR) from an incremental pg_basebackup backup. (CLUS-7224)
    • Create a new cluster directly from an incremental pg_basebackup backup. (CLUS-7225)
    • Replica compatibility — incremental pg_basebackup now works correctly on a replica even when the primary has summarize_wal disabled. (CLUS-7281)

  • Promote Replica for Valkey / Redis: Valkey (Sentinel and Sharded) and Redis clusters now support promoting a replica to primary from the node's action menu. A confirmation dialog guards against accidental promotion. (CLUS-6951, CLUS-7285)

Improvements

  • PostgreSQL backups dynamically raise wal_keep_size before running pg_basebackup to prevent failure when WAL files are recycled mid-backup; the original value is restored on the target node afterward. (CLUS-7075)
  • Galera package detection has been updated to work with the new Percona repository API, keeping Galera version selection accurate for new deployments and upgrades. (CLUS-7331)

Bug Fixes

Backups

  • Incremental pg_basebackup now succeeds after a prior pg_basebackup restore, so repeated backup/restore cycles work as expected. (CLUS-7300)
  • Creating an incremental pg_basebackup backup for a newly added replica node now succeeds. (CLUS-7364) Added safeguards to prevent incremental pg_basebackup from failing when attempted on a fresh timeline after a restore. (CLUS-7383)
  • The controller is no longer offered as a backup storage host in pool mode for cluster types where it should be disabled, and selecting the controller as storage now correctly sets the cc_storage flag on the backup job. (CLUS-6986)

User Management

  • Creating a new PostgreSQL user in User Management v2 now works reliably. Grants and revokes are always applied at the database level as expected. (CLUS-7231)
  • Deleting a PostgreSQL user that owns no objects no longer fails — privileges are now explicitly revoked before the user is dropped. (CLUS-7232)
  • Cluster permission level no longer unexpectedly switches from Read-Only to Custom in User Management when new clusters are added; existing non-custom teams are now correctly reflected on new clusters. (CLUS-7077)
  • Fixed a syntax error when creating a MySQL user with "No privileges" selected. (CLUS-7076)

Security & Access Control

  • View-only users can no longer kill a database query — execution permissions on the qm_killprocess and qm_purge actions have been tightened. (CLUS-7244)
  • View-only users can no longer delete database users. The DB Users screen now correctly enforces read-only access across Galera, MySQL Replication, and PostgreSQL Streaming Replication clusters. (CLUS-7290)
  • Credential passwords are now consistently masked in error reports when the masking option is enabled — previously some passwords could leak through unmasked. (CLUS-6958)

Certificates

  • A previously created Certificate Authority can now be selected as the issuer when generating server or client certificates. Selecting the CA from the side menu no longer replaces it with a self-signed certificate. (CLUS-7252)

Replication & Stability

  • Adding a PostgreSQL replica to a cluster under load no longer times out, and the wal_keep pre-flight warning has been corrected for PostgreSQL 13 and later. (CLUS-7277)
  • Fixed a UI crash that could occur when switching from PostgreSQL user management to a Valkey cluster that had failed. (CLUS-7365)

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_messages table 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)

    • Improvements

      • PostgreSQL Backup Reliability - Updated pg_basebackup to 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)

  • 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.

Copyright © 2014-2026 Severalnines AB. All rights reserved.

Severalnines and ClusterControl are registered trademarks in the US, UK, and EU. The 3rd-party trademarks on this site are property of their respective owners and are used for referential purposes only.

Made with Material for MkDocs