Skip to content

Latest commit

 

History

History
116 lines (89 loc) · 7.27 KB

v1.2.1.md

File metadata and controls

116 lines (89 loc) · 7.27 KB

Harvester v1.2.1 Release Note

This release follows Harvester v1.2.0, the documentation is available at https://docs.harvesterhci.io/v1.2.

Rancher Support

If you are using Rancher for multi-cluster management of Harvester, you must upgrade the Rancher server to v2.7.6 or later first before upgrading the Harvester to v1.2.1.

For more details about the Harvester & Rancher support matrix, please visit our website here.

Downloads

ISO

💿 harvester-v1.2.1-amd64.iso

Additional Artifacts

📁 https://releases.rancher.com/harvester/v1.2.1/harvester-v1.2.1-vmlinuz-amd64 📁 https://releases.rancher.com/harvester/v1.2.1/harvester-v1.2.1-initrd-amd64 📁 https://releases.rancher.com/harvester/v1.2.1/harvester-v1.2.1-rootfs-amd64.squashfs 📁 https://releases.rancher.com/harvester/v1.2.1/harvester-v1.2.1-amd64.raw.zsthttps://releases.rancher.com/harvester/v1.2.1/harvester-v1.2.1-amd64.sha512 📝 https://releases.rancher.com/harvester/v1.2.1/version.yaml

Install

Harvester can be installed with the ISO image or via PXE boot.

Highlights

  • Add debug parameter with elemental command. See #4541.
  • v1.2.1 upgrade related enhancements. See Bug Fixes.

Upgrade

Upgrade from v1.2.0 to v1.2.1

Bug Fixes

Upgrade:

  • Upgrade to Harvester 1.2.0 fails in fleet-agent due to customer provided SSL certificate without IP SAN. See #4519.
  • fleet-controller complains "missing apiServerURL" after the upgrade. See #4565.
  • Upgrade stuck with first node in Post-draining state. See #4526.

Installation:

  • The Harvester ISO boot extremly slow on Dell XR4000. See #4586.
  • v1.2.0 Interactive ISO Fails to Install On Some Bare-Metal Devices. See #4510.

Documentation

  • Unable to join new v1.2.0 node to v1.2.0 cluster. See #4511. [doc]
  • Upgrade stuck with first node in Post-draining state. See #4526. [doc]
  • VMDP Image wrong after upgrade to Harvester 1.2.0. See #4534. [doc]

Known Issues

  • When multiple rke2 clusters exist in the same namespace, an re-sync topology error: nodes not found in cloud-provider occurs where the nodes cannot be found in the cloud-provider controller. See #4459.
  • Fail to scale down RKE2 Harvester node driver cluster. See #4358.
  • Failed to pass guest cluster name into Harvester cloud provider. See #4232.
  • Unable to access Node IP addresses over HTTPS on VM router in the Harvester cluster. See #3960 [Workaround].
  • Unable to select Harvester Cloud Provider in Rancher 2.7.x. See #3750 [Workaround].
  • Harvester upgrade may stuck in another operation (install/upgrade/rollback) by fleet. See #3675 [Workaround].
  • Upgrade issues:

Dependency Component Versions

Component Version
Longhorn v1.4.3
KubeVirt v0.54.0
Embedded Rancher v2.7.5
RKE2 v1.25.9+rke2r1

Contributors

@albinsun @bk201 @chrisho @connorkuehl @DaiYuzeng @FrankYang0529 @futuretea @guangbochen @ibrokethecloud @irishgordo @jeff-radick-suse @jillian-maroket @khushboo-rancher @lanfon72 @LucasSaintarbor @mantis-toboggan-md @markhillgit @masteryyh @n313893254 @noahgildersleeve @rebeccazzzz @starbops @TachunLin @Vicente-Cheng @vickyhella @w13915984028 @WebberHuang1118 @WuJun2016 @yaocw2020 @yasker