Longhorn v1.7.x

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 04 September 2025, one year and six months after the release of the first stable version.

Release	Released
1.7.2 - Stable	17 Oct 2024
1.7.1 - Stable	04 Sept 2024
1.7.0	20 Aug 2024

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.

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
Oracle Linux	9.4
RHEL	9.3
Rocky Linux	9.3
SLE Micro	6.0
SLES	15 SP6
Ubuntu	22.04
Talos	1.7
Container-Optimized OS (GKE)	113

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 document at https://longhorn.io/docs/1.7.1/best-practices/. If any preview or experimental features require additional resource requirements, please check the corresponding document to adjust the setup such as the Longhorn v2 data engine, https://longhorn.io/docs/1.7.2/spdk/prerequisites/.

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