Harvester v1.1.x

Product Lifecycle & Support Phases

All Harvester 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 June 2024.

Release	Released
1.1.3 - Latest	21 Dec 2023
1.1.2 - *Stable*	25 Apr 2023
1.1.1	01 Dec 2022
1.1.0	26 Oct 2022

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.

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

Scope of Support

A Harvester support entitlement includes support for the components that are bundled with the Harvester appliance. Certain components such as Longhorn storage are subject to additional usage based entitlement, see SUSE T&C or speak to your Account Executive for details.

Hypervisor Host OS
Storage (Longhorn)
Harvester cloud provider (CCM) and storage interface (CSI)
Terraform provider
Windows VMDP Drivers

Support for guest Kubernetes distributions (e.g. RKE2, k3s) or Rancher Manager require a separate entitlement in addition to Harvester.

Harvester & Rancher Support Matrix

Rancher is an open-source multi-cluster management platform. Harvester has integrated Rancher by default starting with Rancher v2.6.1.

Harvester Version	Rancher Version	Harvester Node Driver Supported K8S Versions
v1.1.3	v2.6.11, v2.6.13, v2.7.9	RKE1 & RKE2 v1.23, v1.24 (<v1.24.15+rke2r1)
v1.1.2	v2.6.11, v2.7.3, v2.7.4, v2.7.9	RKE1 & RKE2 v1.23, v1.24 (<v1.24.15+rke2r1)
v1.1.1	v2.6.9, v2.6.11, v2.7.3	RKE1 & RKE2 v1.23, v1.24 (<v1.24.15+rke2r1)

Rancher Manager Supported Deployment

If a Harvester cluster requires Rancher Manager to be deployed on it, we support the following configuration:

3 node/VM RKE2 or k3s cluster
Installed using the Rancher Helm chart according to the Rancher Documentation
Single node Rancher managers are not supported

Harvester CCM & CSI Driver

CCM and CSI drivers support RKE1, RKE2 and k3s distributions unless otherwise noted

For Harvester CCM and CSI driver integration with RKE1, please install or upgrade to the latest chart manually from the Catalog Apps. Refer to the Harvester doc here for more details.

Starting with Harvester v1.1.2 and Rancher v2.7+, please upgrade your RKE2 cluster to the following versions for the best Harvester cloud provider & CSI driver capability support.

RKE2 Version	Harvester Cloud Provider	Harvester CSI Driver	Feature Upgrade Support
>=v1.26.1+rke2r1 && <v1.26.6+rke2r1	v0.1.14	v0.1.16	Yes
>=v1.25.6+rke2r1 && <v1.25.11+rke2r1	v0.1.14	v0.1.16	Yes
>=v1.24.10+rke2r1 && <v1.24.15+rke2r1	v0.1.14	v0.1.16	Yes
>=v1.23.16+rke2r1	v0.1.13	v0.1.16	Yes
>=v1.22.12+rke2r1	v0.1.13	v0.1.11	No(EOL)
>=v1.21.12+rke2r1	v0.1.11	v0.1.11	No(EOL)

Other Dependency Versions

Harvester Version	Harvester Terraform Provider
v1.1.3	v0.6.4
v1.1.2	v0.6.2
v1.1.1	v0.6.0

Guest Operating System Support

Full support for the following guest operating systems that have been validated to run in Harvester:

OS Family	Version
SLES	15 SP4
OpenSUSE Leap	15.4
Windows Server	2012 2016 2019 2022
Windows (workstation)	10 11

All other x86 operating systems are supported on a "best effort" basis.

Hardware Requirements

For best results, SUSE recommends using YES certified for SLES 15 SP3 or SP4 Hardware with Harvester: https://www.suse.com/yessearch/. Harvester is built on SLE technology and YES certified hardware has additional validation of driver and system board compatibility.

For production use cases, the following minimum hardware is required. R&D and evaluation environments may use smaller specs if needed.

Type	Requirements
Cluster	Minimum of 3 servers in each cluster
CPU	x86_64 only. Hardware-assisted virtualization is required. 8-core processor minimum for testing; 16-core or above is required
Memory	32 GB minimum, 64 GB or above required
Disk Capacity	200 GB minimum for testing, 500 GB or above required for production. Custom partitioning not supported.
Disk Performance	5,000+ random IOPS per disk(SSD/NVMe). Management nodes (first 3 nodes) must be fast enough for Etcd. Only local disks or Hardware RAID is supported.
Network Card	1Gbps Ethernet minimum for testing, 10Gbps Ethernet minimum required for production.
Network Switch	Trunking of ports required for VLAN support

We recommend server-class hardware for the best results. Laptops and nested virtualization are not officially supported.

Support Matrix

RANCHER 2.9.X

RANCHER 2.8.X

RANCHER 2.7.X

RANCHER 2.6.X

RANCHER 2.5.X

RANCHER 2.4.X

RKE 1

RKE 2

K3S

HARVESTER

LONGHORN

NEUVECTOR