From b6ae56f113ad9cbb2d98dd29124982eb1ce882eb Mon Sep 17 00:00:00 2001 From: Derek Su Date: Thu, 2 Nov 2023 12:00:50 +0800 Subject: [PATCH] Add note for longhorn-system upgrade for v2 volumes Longhorn 7025 Signed-off-by: Derek Su --- content/docs/1.5.0/deploy/important-notes/index.md | 4 ++++ content/docs/1.5.0/deploy/upgrade/_index.md | 4 ++++ content/docs/1.5.1/deploy/important-notes/index.md | 4 ++++ content/docs/1.5.1/deploy/upgrade/_index.md | 4 ++++ content/docs/1.5.2/deploy/important-notes/index.md | 4 ++++ content/docs/1.5.2/deploy/upgrade/_index.md | 5 +++++ 6 files changed, 25 insertions(+) diff --git a/content/docs/1.5.0/deploy/important-notes/index.md b/content/docs/1.5.0/deploy/important-notes/index.md index 7c9840268..332771768 100644 --- a/content/docs/1.5.0/deploy/important-notes/index.md +++ b/content/docs/1.5.0/deploy/important-notes/index.md @@ -12,6 +12,10 @@ 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 + +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. + ### Attachment/Detachment Refactoring Side Effect On The Upgrade Process In Longhorn v1.5.0, we refactored the internal volume attach/detach mechanism. diff --git a/content/docs/1.5.0/deploy/upgrade/_index.md b/content/docs/1.5.0/deploy/upgrade/_index.md index 4014cc65b..99d46aea0 100644 --- a/content/docs/1.5.0/deploy/upgrade/_index.md +++ b/content/docs/1.5.0/deploy/upgrade/_index.md @@ -56,6 +56,10 @@ 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. + # Extended Reading Visit [Some old instance manager pods are still running after upgrade](https://longhorn.io/kb/troubleshooting-some-old-instance-manager-pods-are-still-running-after-upgrade) for more information about the cleanup strategy of instance manager pods during upgrade. diff --git a/content/docs/1.5.1/deploy/important-notes/index.md b/content/docs/1.5.1/deploy/important-notes/index.md index 7c9840268..332771768 100644 --- a/content/docs/1.5.1/deploy/important-notes/index.md +++ b/content/docs/1.5.1/deploy/important-notes/index.md @@ -12,6 +12,10 @@ 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 + +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. + ### Attachment/Detachment Refactoring Side Effect On The Upgrade Process In Longhorn v1.5.0, we refactored the internal volume attach/detach mechanism. diff --git a/content/docs/1.5.1/deploy/upgrade/_index.md b/content/docs/1.5.1/deploy/upgrade/_index.md index 94c51ed35..9bfd0cbd8 100644 --- a/content/docs/1.5.1/deploy/upgrade/_index.md +++ b/content/docs/1.5.1/deploy/upgrade/_index.md @@ -56,6 +56,10 @@ 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. + # Extended Reading Visit [Some old instance manager pods are still running after upgrade](https://longhorn.io/kb/troubleshooting-some-old-instance-manager-pods-are-still-running-after-upgrade) for more information about the cleanup strategy of instance manager pods during upgrade. diff --git a/content/docs/1.5.2/deploy/important-notes/index.md b/content/docs/1.5.2/deploy/important-notes/index.md index e2305db94..11c256957 100644 --- a/content/docs/1.5.2/deploy/important-notes/index.md +++ b/content/docs/1.5.2/deploy/important-notes/index.md @@ -12,6 +12,10 @@ 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 + +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. + ### Offline Upgrade Required To Fully Prevent Unexpected Replica Expansion Longhorn v1.5.2 introduces a new mechanism to prevent [unexpected replica diff --git a/content/docs/1.5.2/deploy/upgrade/_index.md b/content/docs/1.5.2/deploy/upgrade/_index.md index 94c51ed35..be2de89b8 100644 --- a/content/docs/1.5.2/deploy/upgrade/_index.md +++ b/content/docs/1.5.2/deploy/upgrade/_index.md @@ -56,6 +56,11 @@ 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. + + # Extended Reading Visit [Some old instance manager pods are still running after upgrade](https://longhorn.io/kb/troubleshooting-some-old-instance-manager-pods-are-still-running-after-upgrade) for more information about the cleanup strategy of instance manager pods during upgrade.