doc: update upgrade for v2 volumes

Longhorn 7094 Signed-off-by: Derek Su <[email protected]>
longhorn · Nov 17, 2023 · f42b100 · f42b100
1 parent d54a737
commit f42b100
Show file tree

Hide file tree

Showing 8 changed files with 16 additions and 18 deletions.
diff --git a/content/docs/1.5.0/deploy/important-notes/index.md b/content/docs/1.5.0/deploy/important-notes/index.md
@@ -12,9 +12,9 @@ Please see [here](https://github.com/longhorn/longhorn/releases/tag/v{{< current
 
 Please ensure your Kubernetes cluster is at least v1.21 before upgrading to Longhorn v{{< current-version >}} because this is the minimum version Longhorn v{{< current-version >}} supports.
 
-### Detach All V2 Volumes Before Upgrade
+### Detach All V1 and V2 Volumes When v2-data-engine is Enabled Before Upgrade
 
-Please note that Longhorn does not support the upgrade when v2 volumes are attached. Prior to initiating the upgrade process, ensure that all v2 volumes are detached.
+Longhorn does not support upgrading with v1 or v2 volumes attached when the V2 Data Engine is enabled. Detach all volumes before upgrading.
 
 ### Attachment/Detachment Refactoring Side Effect On The Upgrade Process
 

diff --git a/content/docs/1.5.0/deploy/upgrade/_index.md b/content/docs/1.5.0/deploy/upgrade/_index.md
@@ -56,9 +56,9 @@ During the upgrade, Longhorn will automatically:
 
 Visit [Recurring Snapshots and Backups](../../snapshots-and-backups/scheduling-backups-and-snapshots) for more information about the new `Recurring Job` feature.
 
-## 5. Detach All V2 Volumes Before Upgrade
+## 5. Detach All V1 and V2 Volumes When v2-data-engine is Enabled Before Upgrade
 
-Please note that Longhorn does not support the upgrade when v2 volumes are attached. Prior to initiating the upgrade process, ensure that all v2 volumes are detached. 
+Longhorn does not support upgrading with v1 or v2 volumes attached when the V2 Data Engine is enabled. Detach all volumes before upgrading.
 
 # Extended Reading
 

diff --git a/content/docs/1.5.1/deploy/important-notes/index.md b/content/docs/1.5.1/deploy/important-notes/index.md
@@ -12,9 +12,9 @@ Please see [here](https://github.com/longhorn/longhorn/releases/tag/v{{< current
 
 Please ensure your Kubernetes cluster is at least v1.21 before upgrading to Longhorn v{{< current-version >}} because this is the minimum version Longhorn v{{< current-version >}} supports.
 
-### Detach All V2 Volumes Before Upgrade
+### Detach All V1 and V2 Volumes When v2-data-engine is Enabled Before Upgrade
 
-Please note that Longhorn does not support the upgrade when v2 volumes are attached. Prior to initiating the upgrade process, ensure that all v2 volumes are detached.
+Longhorn does not support upgrading with v1 or v2 volumes attached when the V2 Data Engine is enabled. Detach all volumes before upgrading.
 
 ### Attachment/Detachment Refactoring Side Effect On The Upgrade Process
 

diff --git a/content/docs/1.5.1/deploy/upgrade/_index.md b/content/docs/1.5.1/deploy/upgrade/_index.md
@@ -56,9 +56,9 @@ During the upgrade, Longhorn will automatically:
 
 Visit [Recurring Snapshots and Backups](../../snapshots-and-backups/scheduling-backups-and-snapshots) for more information about the new `Recurring Job` feature.
 
-## 5. Detach All V2 Volumes Before Upgrade
+## 5. Detach All V1 and V2 Volumes When v2-data-engine is Enabled Before Upgrade
 
-Please note that Longhorn does not support the upgrade when v2 volumes are attached. Prior to initiating the upgrade process, ensure that all v2 volumes are detached. 
+Longhorn does not support upgrading with v1 or v2 volumes attached when the V2 Data Engine is enabled. Detach all volumes before upgrading.
 
 # Extended Reading
 

diff --git a/content/docs/1.5.2/deploy/important-notes/index.md b/content/docs/1.5.2/deploy/important-notes/index.md
@@ -12,9 +12,9 @@ Please see [here](https://github.com/longhorn/longhorn/releases/tag/v{{< current
 
 Please ensure your Kubernetes cluster is at least v1.21 before upgrading to Longhorn v{{< current-version >}} because this is the minimum version Longhorn v{{< current-version >}} supports.
 
-### Detach All V2 Volumes Before Upgrade
+### Detach All V1 and V2 Volumes When v2-data-engine is Enabled Before Upgrade
 
-Please note that Longhorn does not support the upgrade when v2 volumes are attached. Prior to initiating the upgrade process, ensure that all v2 volumes are detached.
+Longhorn does not support upgrading with v1 or v2 volumes attached when the V2 Data Engine is enabled. Detach all volumes before upgrading.
 
 ### Offline Upgrade Required To Fully Prevent Unexpected Replica Expansion
 

diff --git a/content/docs/1.5.2/deploy/upgrade/_index.md b/content/docs/1.5.2/deploy/upgrade/_index.md
@@ -56,10 +56,9 @@ During the upgrade, Longhorn will automatically:
 
 Visit [Recurring Snapshots and Backups](../../snapshots-and-backups/scheduling-backups-and-snapshots) for more information about the new `Recurring Job` feature.
 
-## 5. Detach All V2 Volumes Before Upgrade
-
-Please note that Longhorn does not support the upgrade when v2 volumes are attached. Prior to initiating the upgrade process, ensure that all v2 volumes are detached. 
+## 5. Detach All V1 and V2 Volumes When v2-data-engine is Enabled Before Upgrade
 
+Longhorn does not support upgrading with v1 or v2 volumes attached when the V2 Data Engine is enabled. Detach all volumes before upgrading.
 
 # Extended Reading
 

diff --git a/content/docs/1.5.3/deploy/important-notes/index.md b/content/docs/1.5.3/deploy/important-notes/index.md
@@ -12,9 +12,9 @@ Please see [here](https://github.com/longhorn/longhorn/releases/tag/v{{< current
 
 Please ensure your Kubernetes cluster is at least v1.21 before upgrading to Longhorn v{{< current-version >}} because this is the minimum version Longhorn v{{< current-version >}} supports.
 
-### Detach All V2 Volumes Before Upgrade
+### Detach All V1 and V2 Volumes When v2-data-engine is Enabled Before Upgrade
 
-Please note that Longhorn does not support the upgrade when v2 volumes are attached. Prior to initiating the upgrade process, ensure that all v2 volumes are detached.
+Longhorn does not support upgrading with v1 or v2 volumes attached when the V2 Data Engine is enabled. Detach all volumes before upgrading.
 
 ### Offline Upgrade Required To Fully Prevent Unexpected Replica Expansion
 

diff --git a/content/docs/1.5.3/deploy/upgrade/_index.md b/content/docs/1.5.3/deploy/upgrade/_index.md
@@ -56,10 +56,9 @@ During the upgrade, Longhorn will automatically:
 
 Visit [Recurring Snapshots and Backups](../../snapshots-and-backups/scheduling-backups-and-snapshots) for more information about the new `Recurring Job` feature.
 
-## 5. Detach All V2 Volumes Before Upgrade
-
-Please note that Longhorn does not support the upgrade when v2 volumes are attached. Prior to initiating the upgrade process, ensure that all v2 volumes are detached. 
+## 5. Detach All V1 and V2 Volumes When v2-data-engine is Enabled Before Upgrade
 
+Longhorn does not support upgrading with v1 or v2 volumes attached when the V2 Data Engine is enabled. Detach all volumes before upgrading.
 
 # Extended Reading