SUSE has released Harvester 1.9.1, its open-source hyperconverged infrastructure platform for running virtual machines on Kubernetes, and announced that community releases and builds of its commercial product, SUSE Virtualization, will now come from separate build pipelines. The practical result for admins is a new upgrade path: a Harvester 1.9.1 cluster cannot be switched directly to SUSE Virtualization 1.9.1, though it can upgrade to SUSE Virtualization 1.10.1, targeted for February 2027.
Key points on Harvester 1.9.1 and SUSE Virtualization in 20 seconds
- Harvester 1.9.1 is out, and SUSE says it will remain 100% open source.
- SUSE Virtualization 1.9.1 arrives in November for fresh installs only.
- Harvester 1.9.1 cannot move to SUSE Virtualization 1.9.1, but it can upgrade to 1.10.1.
- The change is driven by the EU Cyber Resilience Act and SLSA Level 3 requirements.
Harvester combines KubeVirt for virtualization, Longhorn for distributed block storage and RKE2 as its Kubernetes distribution, and it has become one of the open alternatives many teams evaluate to move off VMware after Broadcom’s acquisition. SUSE sells it with support as SUSE Virtualization, and until now both shared the same code and the same builds.
Schedule and upgrade paths
According to Alex Settle’s post on the Rancher blog, published on November 13, the schedule is:
| Release | Timing |
|---|---|
| Harvester 1.9.1 | Available now |
| SUSE Virtualization 1.9.1 | November 2026, fresh installs only |
| Harvester 1.10.0 | Target: December 2026 |
| SUSE Virtualization 1.10.1 | Target: February 2027 |
The key rule: if you run a Harvester 1.9.1 cluster today and want to move to the commercial product, you cannot switch directly to SUSE Virtualization 1.9.1. You will need to wait for 1.10.1, to which SUSE will fully support upgrades from both Harvester 1.9.1 and SUSE Virtualization 1.9.1. For production environments that rely on SUSE support, plan around that schedule before upgrading.
Why SUSE is splitting the builds
SUSE points to two requirements: the European Union’s Cyber Resilience Act (CRA), which will place security and vulnerability-handling obligations on vendors of software sold in the EU, and SLSA Level 3, a framework that calls for verifiable, tamper-resistant build processes in the software supply chain. Separate pipelines let SUSE apply those controls to the commercial product without imposing them on the community project.
The announcement does not list what is new in 1.9.1 or the KubeVirt, Longhorn or RKE2 versions, so check the GitHub release notes before upgrading. SUSE Virtualization customers who need SLA-backed support should open tickets in the SUSE Customer Center or contact their technical account manager, and SUSE promises a follow-up post for them.
FAQ
Can I move from Harvester 1.9.1 to SUSE Virtualization 1.9.1?
No. SUSE Virtualization 1.9.1 is for fresh installs only. The supported path is upgrading to SUSE Virtualization 1.10.1, targeted for February 2027.
Is Harvester still open source?
Yes. SUSE says Harvester is and will remain 100% open source.
Why is SUSE separating the releases?
To meet EU Cyber Resilience Act and SLSA Level 3 requirements for the commercial product’s build pipeline.
Sources:
