Here we cover how to upgrade to the latest Longhorn from all previous releases.
There are no deprecated or incompatible changes introduced in v1.3.0.
There are normally two steps in the upgrade process: first upgrade Longhorn manager to the latest version, then manually upgrade the Longhorn engine to the latest version using the latest Longhorn manager.
After Longhorn Manager is upgraded, Longhorn Engine also needs to be upgraded using the Longhorn UI.
Since Longhorn v1.1.1, we provide an option to help you automatically upgrade engines
With the introduction of the new label-driven
Recurring Job feature, Longhorn has removed the
RecurringJobs field in the Volume Spec and planned to deprecate
RecurringJobs in the StorageClass.
During the upgrade, Longhorn will automatically:
recurringJobsfield in Volume Spec and convert them to the volume labels.
recurringJobsin the StorageClass and convert them to the new
Visit Recurring Snapshots and Backups for more information about the new
Recurring Job feature.
Visit Some old instance manager pods are still running after upgrade for more information about the cleanup strategy of instance manager pods during upgrade.
If you have any issues, please report it at https://github.com/longhorn/longhorn/issues and include your backup yaml files as well as manager logs.
© 2019-2023 Longhorn Authors | Documentation Distributed under CC-BY-4.0
© 2023 The Linux Foundation. All rights reserved. The Linux Foundation has registered trademarks and uses trademarks. For a list of trademarks of The Linux Foundation, please see our Trademark Usage page.