JUMP TO
Support Matrix

Harvester v1.3.x

IMPORTANT: Harvester only allows upgrades from supported versions. For more information about upgrade paths and procedures, see Upgrading Harvester. 

Harvester supports upgrades from v1.2.2 to v1.3.1 and from v1.3.0 to v1.3.1. Harvester does NOT support upgrades from v1.2.1 to v1.3.0, from v1.2.1 to v1.3.1, or from v1.2.2 to v1.3.0.

The documentation contains information about upgrade-related issues. If you are upgrading from v1.2.2 to v1.3.1 or from v1.3.0 to v1.3.1 and your cluster is affected by issue #6041, check the suggested workaround in the documentation. If you are upgrading from v1.3.1 to v1.3.2 and you encounter issue #6432 while upgrading a two-node cluster, follow the suggested workaround. 

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.

The current stable release is v1.3.1.

All versions listed below have an EOL date of 13 June 2025.

ReleaseReleased
1.3.2. - Latest6 Sept 2024
1.3.1 - Stable13 June 2024
1.3.0 15 March 2024

Harvester follows an N -1 support policy (meaning that the 2 most recent minor versions receive security and bug fixes) along with a 26-week release cycle. This results in a release being supported for 14 months (12 months of support and 2 months of upgrade period).

PHASESDESCRIPTION
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 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.

IMPORTANT: If you are using Rancher v2.7.11 with Harvester, AVOID upgrading to Rancher v2.8.2. A known issue, #5347, results in all downstream cluster nodes being replaced by Rancher (one at a time).

Harvester VersionRancher VersionHarvester Node Driver Supported K8S Versions
v1.3.2v2.7.15, v2.8.6, v2.9.1RKE1 & RKE2 v1.27, v1.28, v1.29, v1.30
v1.3.1v2.7.12, v2.7.13, 2.7.14, v2.8.2, v2.8.3, v2.8.4, 2.8.5RKE1 & RKE2 v1.26, v1.27, v1.28, v1.29
v1.3.0v2.7.9, v2.7.10, v2.7.11, v2.8.1, v2.8.2RKE1 & RKE2 v1.26, v1.27, v1.28
 

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 Drivers

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.2.0 + Rancher v2.7.6, please choose your RKE2 cluster to the following versions for the best Harvester cloud provider & CSI driver capability support.

Harvester Cloud ProviderHarvester CSI DriverRKE2 VersionFeature Upgrade Support
v0.2.4v0.1.18>=v1.27.16+rke2r2Yes
v0.2.4v0.1.17>=v1.26.15+rke2r1Yes
v0.2.3v0.1.17>=v1.26.6+rke2r1Yes
v0.2.2v0.1.16>=v1.26.6+rke2r1Yes
v0.2.2v0.1.16>=v1.25.11+rke2r1Yes
v0.2.2v0.1.16>=v1.24.15+rke2r1Yes
v0.1.14v0.1.15>=v1.23.17+rke2r1No

For the RKE2 cluster versions with Harvester v1.1.2, please refer to the v1.1.x support matrix for more details.

Other Dependency Versions

 
Harvester VersionHarvester Terraform Provider
v1.3.2v0.6.4
v1.3.1v0.6.4
v1.3.0v0.6.4
 

Guest Operating System Support

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

OS FamilyVersions Supported in v1.3.2Versions Supported in v1.3.0 and v1.3.1
SLES15 SP6
15 SP4

15 SP5

15 SP4

OpenSUSE Leap 15.515.4
SLE Micro6 
Ubuntu24.04

22.04

23.04

RHEL9.4 
Windows Server20222022
Windows (workstation)1111

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. 

To get the Harvester server up and running, the following minimum hardware is required:

TypeRequirements
ClusterMinimum of 3 servers in each cluster
CPUx86_64 only. Hardware-assisted virtualization is required. 8-core processor minimum for testing; 16-core or above is required
Memory32 GB minimum, 64 GB or above required
Disk Capacity200 GB minimum for testing (180 GB minimum when using multiple disks); 500 GB or above is required for production.
Disk Performance5,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 Card1 Gbps Ethernet minimum for testing, 10Gbps Ethernet minimum required for production. 
Network SwitchTrunking of ports required for VLAN support

Testing environments with 1 GB NIC / 140 GB disk are not supported

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