We only support upgrading to v1.1.1 from v1.0.x. For other versions, please upgrade to v1.0.x first.
Engine live upgrade is supported from v1.0.x to v1.1.1.
For airgap upgrades when Longhorn is installed as a Rancher app, you will need to modify the image names and remove the registry URL part.
For example, the image registry.example.com/longhorn/longhorn-manager:v1.1.1 is changed to longhorn/longhorn-manager:v1.1.1 in Longhorn images section. For more information, see the air gap installation steps here.
Preparing for the Upgrade
If Longhorn was installed using a Helm Chart, or if it was installed as Rancher catalog app, check to make sure the parameters in the default StorageClass weren’t changed. Changing the default StorageClass’s parameter might result in a chart upgrade failure. if you want to reconfigure the parameters in the StorageClass, you can copy the default StorageClass’s configuration to create another StorageClass.
The current default StorageClass has the following parameters:
numberOfReplicas: <user specified replica count, 3 by default>
Prerequisite: Always back up volumes before upgrading. If anything goes wrong, you can restore the volume using the backup.
To avoid crashing existing volumes, as well as switch from the deprecated setting Guaranteed Engine CPU to the new instance manager CPU reservation mechanism, Longhorn will automatically set Engine Manager CPU Request and Replica Manager CPU Request from each node based on the deprecated setting value during upgrade. Then, the new global instance manager CPU settings Guaranteed Engine Manager CPU and Guaranteed Replica Manager CPU won’t take effect.
You may need to check the new mechanism and the setting descriptions to see if you need any adjustments.
Error: "longhorn" is invalid: provisioner: Forbidden: updates to provisioner are forbidden.
This means there are some modifications applied to the default storageClass and you need to clean up the old one before upgrade.
To clean up the deprecated StorageClass, run this command: