Product Lifecycle & Support Phases
All Longhorn releases will go through three stages: In Development, Latest, and then finally Stable. Please ensure you do not upgrade your production cluster to anything other than a listed Stable version. Use Latest versions for test purposes only.
All versions listed below have an EOL date of 01 August 2025, one year and six months after the release of the first stable version.
|1.6.0 - Latest
|01 Feb 2024
|GA to EOM
Upon General Availability of all major and minor releases, products are fully supported and maintained until the End of Maintenance date. Support entails general troubleshooting of a specific issue to isolate potential causes. Issue resolution is pursued through one or more of the following:
|EOM to EOL
After a product release reaches its End of Maintenance date, no further code-level maintenance will be provided, except for critical security-related fixes on a request basis. Product will continue to be supported until it reaches End of Life, in the form of:
Once a product release reaches its End of Life date, the customer may continue to use the product within the terms of product licensing agreement.
- Support Plans from SUSE do not apply to product releases past their EOL date.
Scope of Support
A Longhorn support entitlement includes Longhorn components and the following operating systems and platform architectures. Furthermore, Longhorn is supported to run on any certified Kubernetes distributions and versions, such as the actively supported versions of RKE2 and K3s. Experimental or Preview features are not eligible for support.
Verified Operating Systems
The following Linux OS distributions and versions have been verified during release testing. However, this does not imply that Longhorn exclusively supports these distributions. Essentially, Longhorn should function well on any certified Kubernetes cluster running on Linux nodes with a wide range of general-purpose operating systems, as well as verified container-optimized operating systems like SLE Micro.
Supported Platform Architectures
To get a Longhorn cluster up and running with the supported features, the following minimum hardware is required. For other best practices, please refer to the official document at https://longhorn.io/docs/1.6.0/best-practices/. If any preview or experimental features require additional resource requirements, please check the corresponding document to adjust the setup.
|3 Nodes for running Longhorn components
|4 CPUs per node
|4 GiB per node
|Local SSD/NVMe disks are highly recommended for optimal storage performance of volumes