ivampiresp/longhorn
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

doc: Make sure user understand v0.5.0 to v0.6.0 needs offline upgrade

Browse Source 
Signed-off-by: Sheng Yang <sheng.yang@rancher.com>
This commit is contained in:
Sheng Yang 2019-09-21 14:54:13 -07:00 committed by Sheng Yang
parent bac4f8cd3f
commit c2e5a610a8
2 changed files with 6 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
README.md
View File

@ -122,10 +122,6 @@ Noted that the UI is unauthenticated when you installed Longhorn using YAML file
# Upgrade # Upgrade
Since v0.3.3, Longhorn is able to perform fully-automated non-disruptive upgrades, meaning that the upgrade process won't disrupt the running volumes. Existing volumes continue to run even as the software that implements these volumes are upgraded.
If you're upgrading from Longhorn v0.3.0 or newer:
## Upgrade Longhorn manager ## Upgrade Longhorn manager
##### On Kubernetes clusters Managed by Rancher 2.1 or newer ##### On Kubernetes clusters Managed by Rancher 2.1 or newer
@ -143,7 +139,8 @@ helm upgrade longhorn ./longhorn/chart
## Upgrade Longhorn engine ## Upgrade Longhorn engine
After upgraded manager, follow [the steps here](docs/upgrade.md#upgrade-longhorn-engine) to upgrade Longhorn engine for existing volumes. After upgraded manager, follow [the steps here](docs/upgrade.md#upgrade-longhorn-engine) to upgrade Longhorn engine for existing volumes.
1. For non distruptive upgrade, follow [the live upgrade steps here](./docs/upgrade.md#live-upgrade) 1. Upgrade v0.5.0 to v0.6.0 requires offline upgrade. Live upgrade is not supported for this upgrade.
2. For non distruptive upgrade from previous version to v0.5.0, follow [the live upgrade steps here](./docs/upgrade.md#live-upgrade)
For more details about upgrade in Longhorn or upgrade from older versions, [see here](docs/upgrade.md). For more details about upgrade in Longhorn or upgrade from older versions, [see here](docs/upgrade.md).

4
docs/upgrade.md
View File

@ -27,7 +27,7 @@ Otherwise you will need to download the yaml file from [the official Longhorn De
**ALWAYS MAKE BACKUPS BEFORE UPGRADE THE ENGINE IMAGES.** **ALWAYS MAKE BACKUPS BEFORE UPGRADE THE ENGINE IMAGES.**
### Offline upgrade ### Offline upgrade
If live upgrade is not available (e.g. before v0.3.3), or the volume stuck in degraded state: If live upgrade is not available (e.g. before v0.3.3 or from v0.5.0 to v0.6.0), or the volume stuck in degraded state:
1. Follow [the detach procedure for relevant workloads](upgrade.md#detach-volumes). 1. Follow [the detach procedure for relevant workloads](upgrade.md#detach-volumes).
2. Select all the volumes using batch selection. Click batch operation button 2. Select all the volumes using batch selection. Click batch operation button
`Upgrade Engine`, choose the engine image available in the list. It's `Upgrade Engine`, choose the engine image available in the list. It's
@ -37,7 +37,7 @@ Any volume not part of a Kubernetes workload must be attached from Longhorn UI.
### Live upgrade ### Live upgrade
Live upgrade is available since v0.3.3. Live upgrade is available since v0.3.3, with the exception of upgrade from v0.5.0 to v0.6.0.
Live upgrade should only be done with healthy volumes. Live upgrade should only be done with healthy volumes.