Release Notes

Use this page as your guide to stay up to date on the latest enhancements and changes, ensuring you can make the most of ClusterControl's powerful capabilities.

Release cycle

We highly advise you to keep up to date with the latest version for the following reasons:

ClusterControl has a short release cycle compared to other software applications (likely a new major release every quarter of the year).
ClusterControl has to keep up with all the latest changes and modifications introduced by supported database and application vendors.
Some of the issues you have encountered may already be fixed in the latest weekly maintenance or major release.

To upgrade ClusterControl to the latest version, see Upgrading ClusterControl.

Latest version support policy

Only the two most recent versions of ClusterControl are actively supported. If you are running an older version, we strongly recommend upgrading to continue receiving bug fixes, security patches, and new features.

Note

New features are introduced exclusively in the latest releases. If you require access to the newest capabilities, ensure you are running one of the two most recent versions.

ClusterControl long-term support (LTS) release

Starting with ClusterControl 2.2.0 LTS in September 2024, we are adopting a Yearly Long-Term Support (LTS) cycle for our product.

Our Long-Term Support (LTS) releases receive extended support, including bug fixes and security patches, for an extended period. Unlike standard releases, which focus on introducing new features and innovation, LTS versions emphasize stability, reliability, and long-term usability.

LTS versioning and support timeline

LTS releases follow an even-numbered minor version scheme, for example, 2.2.0, 2.4.0, 2.6.0, and so on. Each LTS version is supported until the next LTS release is released, at which point the previous LTS enters end-of-life and users are encouraged to migrate to the new LTS.

Info

LTS releases receive security updates and patches only. New features are not backported to LTS versions. If your environment requires the latest features, consider tracking the standard (non-LTS) release channel instead.

Benefits of yearly long-term support releases

With a focus on stability and predictability, especially for businesses and users who rely on ClusterControl in critical environments, the yearly LTS cycle aims to provide:

Stability and Reliability: Each LTS undergoes rigorous testing and validation to meet the highest standards of stability, making it ideal for production environments where reliability is paramount.
Predictability: With a predictable yearly schedule, you can plan upgrades and deployments more effectively, aligning them with your project timelines and minimizing disruptions.
Extended Support: Each LTS version receives full support including critical updates and patches, until the next LTS is released, and potentially longer for critical security fixes.
Security-focused maintenance: LTS versions receive security patches and stability fixes only. All new features are reserved for the latest standard releases.

How it works

First LTS Release: The first yearly LTS was released in Q3 2024 (version 2.2.0), marking the beginning of the new LTS cycle.
Release Schedule: A new LTS is released each year in the third quarter, following an even-numbered minor version pattern (e.g., 2.2.0 → 2.4.0 → 2.6.0). Minor updates and patches are provided throughout the year, focusing on maintaining stability rather than introducing new features.
Support Duration: Each LTS version receives full support for at least 12 months, or until the next LTS is announced, with extended support available for critical security issues beyond this period.

Transitioning to the LTS cycle

For users currently on non-LTS versions (the installer script always installs the latest version), migrating to an LTS release is most easily achieved by updating the ClusterControl repository file to point to the LTS repository named repos-release-lts, which contains only LTS releases. This repository is available at http://repo.severalnines.com/repos-release-lts.

Follow the steps below to transition to an LTS version:

Red Hat/Rocky Linux/AlmaLinuxDebian/Ubuntu

Edit the repository file /etc/yum.repos.d/s9s-repo.repo and change the URL to:
```
http://repo.severalnines.com/repos-release-lts/rpm/os/x86_64
```

Update the software repository:

yum search clustercontrol # check for LTS version and/or clear cache with: yum clean all

Re-install the LTS ClusterControl packages:

yum install s9s-tools clustercontrol2 clustercontrol-controller clustercontrol-ssh clustercontrol-cloud clustercontrol-notifications

Restart the ClusterControl-related services:

systemctl restart cmon cmon-ssh cmon-events cmon-cloud

Edit the repository file /etc/apt/sources.list.d/s9s-repos.list and change the URL to:
```
http://repo.severalnines.com/repos-release-lts/deb
```

Update the software repository:

apt update # update the list of available LTS packages

Re-install the LTS ClusterControl packages:

apt install s9s-tools clustercontrol2 clustercontrol-controller clustercontrol-ssh clustercontrol-cloud clustercontrol-notifications

Restart the ClusterControl-related services:

systemctl restart cmon cmon-ssh cmon-events cmon-cloud