doc: Make sure user understand v0.5.0 to v0.6.0 needs offline upgrade
Signed-off-by: Sheng Yang <sheng.yang@rancher.com>
This commit is contained in:
parent
bac4f8cd3f
commit
c2e5a610a8
11
README.md
11
README.md
@ -50,7 +50,7 @@ The easiest way to install Longhorn is to deploy Longhorn from Rancher Catalog.
|
||||
|
||||
1. On Rancher UI, select the cluster and project you want to install Longhorn. We recommended to create a new project e.g. `Storage` for Longhorn.
|
||||
2. Navigate to the `Catalog Apps` screen. Select `Launch`, find Longhorn in the list. Select `View Details`, then click `Launch`. Longhorn will be installed in the `longhorn-system` namespace.
|
||||
|
||||
|
||||
After Longhorn has been successfully installed, you can access the Longhorn UI by navigating to the `Catalog Apps` screen.
|
||||
|
||||
One benefit of installing Longhorn through Rancher catalog is Rancher provides authentication to Longhorn UI.
|
||||
@ -122,10 +122,6 @@ Noted that the UI is unauthenticated when you installed Longhorn using YAML file
|
||||
|
||||
# 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
|
||||
|
||||
##### On Kubernetes clusters Managed by Rancher 2.1 or newer
|
||||
@ -143,11 +139,12 @@ helm upgrade longhorn ./longhorn/chart
|
||||
|
||||
## Upgrade Longhorn engine
|
||||
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).
|
||||
|
||||
# Create Longhorn Volumes
|
||||
# Create Longhorn Volumes
|
||||
|
||||
Before you create Kubernetes volumes, you must first create a storage class. Use following command to create a StorageClass called `longhorn`.
|
||||
|
||||
|
@ -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.**
|
||||
|
||||
### 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).
|
||||
2. Select all the volumes using batch selection. Click batch operation button
|
||||
`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 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.
|
||||
|
||||
|
Loading…
Reference in New Issue
Block a user