From b7c5424d6e961fdadf36cb6852333ba09270894a Mon Sep 17 00:00:00 2001 From: Sheng Yang Date: Fri, 14 Sep 2018 15:58:17 -0700 Subject: [PATCH] Update upgrade.md --- docs/upgrade.md | 13 ++++++++----- 1 file changed, 8 insertions(+), 5 deletions(-) diff --git a/docs/upgrade.md b/docs/upgrade.md index 755299f..2ce573c 100644 --- a/docs/upgrade.md +++ b/docs/upgrade.md @@ -230,17 +230,20 @@ approximately the same for all workloads. ## Upgrade Engine Images -Note: this is entirely optional. Volumes using old engine images will continue -to function, but won't take advantage of new features, performance enhancements -and bug fixes. - +### Offline upgrade +If live upgrade is not available (e.g. from v0.1/v0.2 to v0.3): 1. Follow [the detach procedure for relevant workloads](upgrade.md#detach-volumes). 2. Select all the volumes using batch selection. Click batch operation button -`Upgrade Engine`, choose the only engine image available in the list. It's +`Upgrade Engine`, choose the engine image available in the list. It's the default engine shipped with the manager for this release. 3. Resume all workloads by reversing the [detach volumes procedure](upgrade.md#detach-volumes). Any volume not part of a Kubernetes workload must be attached from Longhorn UI. +### Live upgrade (expermential feature) +Select all the volumes using batch selection. Click batch operation button +`Upgrade Engine`, choose the engine image available in the list. It's +the default engine shipped with the manager for this release. + ## Note Upgrade is always tricky. Keeping recent backups for volumes is critical. If