Longhorn v1.10.x
Longhorn is adopting a new lifecycle strategy that simplifies version management and upgrades. This strategy includes the following:
- Four-month minor release cadence
- Two-month patch release cadence (best effort)
- Component adoption policy
The following table outlines the supported upgrade paths for SUSE Storage. For more information about installation and upgrades, see the documentation. For information on how to migrate from an installation that uses the Longhorn upstream chart or the Rancher chart from Rancher Apps & Marketplace, see the migration documentation.
| Installed Version | Supported Upgrade Versions |
|---|---|
v1.9 |
v1.10 |
v1.10.x |
v1.10.y (where y is greater then x) |
Product Lifecycle & Support Phases
In earlier versions, the terms Latest and Stable were used to provide guidance for upgrades. Starting with v1.9, the terms Community and Prime are used to differentiate the releases intended for community users and SUSE customers.
NOTE:"Prime" refers to SUSE Rancher Prime, which is SUSE's enterprise container management platform. SUSE Storage is the cloud-native storage product that is part of SUSE Rancher Prime.
| Product | Version | Type | Released |
|---|---|---|---|
SUSE Storage |
v1.10.4 |
Prime |
11 June 2026 |
SUSE Storage |
v1.10.3 |
Prime |
11 May 2026 |
SUSE Storage |
v1.10.2 |
Prime |
28 January 2026 |
SUSE Storage |
v1.10.1 |
Prime |
12 November 2025 |
Longhorn |
v1.10.0 |
Community |
25 September 2025 |
The listed versions all have an EOM date of 12 May 2026 and an EOL date of 12 May 2027.
| PHASES | DESCRIPTION |
|---|---|
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: Applying configuration changes.Upgrade recommendation to an existing newer version of product.Code-level maintenance in the form of product updates; typically, results in a maintenance release, which is a newer version of product that was not existing at the time the issue was encountered. |
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: General troubleshooting of a specific issue to isolate potential causes.Upgrade recommendation to an existing newer version of product - Issue resolution limited to applying configuration changes and/or an upgrade recommendation to an existing newer version of product. |
EOL |
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.
| OPERATING SYSTEM | VERIFIED VERSIONS |
|---|---|
SUSE Linux Enterprise Server |
15 SP6 (v1.10.0–v1.10.2); 15 SP7 (v1.10.0–v1.10.4); 16.0 (v1.10.3–v1.10.4) |
SUSE Linux Enterprise Micro |
6.0, 6.1 |
Red Hat Enterprise Linux |
9.6.0, 10.0.0 |
Ubuntu |
22.04, 24.04 |
Rocky Linux |
10.0 |
Oracle |
9.6 |
Talos |
1.10.6 |
Container-Optimized OS |
121 |
Supported Platform Architectures
- AMD64
- ARM64
Hardware Requirements
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 documentation.
| Type | Requirements |
|---|---|
Cluster |
3 Nodes for running Longhorn components |
CPU |
4 CPUs per node |
Memory |
4 GiB per node |
Disk Performance |
Local SSD/NVMe disks are highly recommended for optimal storage performance of volumes |
Network Card |
10Gbps Ethernet |