## Prerequisites: - [x] PCI enabled - [x] VLAN 1 network on mgmt and 1 network on other NICs - [x] 2 Virtual machines with data and md5sum computed- 1 running, 1 stopped - [x] 1 VM network running on PCI device. - [x] 2 VM backup, snapshots - 1 backup when VM is running and 1 backup when VM is stooped - [x] Enable all the Add-ons ## Steps: - [x] Import Harvester into a Rancher cluster - [x] Create guest cluster (1 control plane, 1 worker) - [x] Deploy load balancer using ip pool - [x] Deploy PVC with Harvester SC and attach with a workload - [x] Upgrade Harvester ## Post upgrade checks: - [x] Dependencies Check - [x] [dependency_charts](https://github.com/harvester/harvester/blob/master/deploy/charts/harvester/values.yaml) - [x] Versions of all the crds - [x] virtual machines should be stopped during the upgrade and on doing restart should be accessible. - [x] Restore the backups, check the data - [x] Image and volume status - [x] Monitoring chart status - [x] VM operations are highlighted and working fine. - [ ] ~~Add a node after the upgrade~~ - [x] Scale up guest cluster - [x] Scale down and up the workloads in the guest cluster. - [x] Reboot the Harvester node. No. | Guest OS | Step 1 | | Step 2 | | Step 3 -- | -- | -- | -- | -- | -- | -- 4 | RHEL 9 RHEL 10 Windows Server 2025 | Harvester v1.7.1 Rancher v2.13.2 Guest RKE2: v1.33 | --> | Harvester v1.7.1 Rancher v2.14.0 Guest RKE2: v1.34 | --> | Harvester v1.8.0 Rancher v2.14.0 Guest RKE2: v1.35
Prerequisites:
Steps:
Post upgrade checks:
Add a node after the upgrade