Docs: Clarify upgrade path into to avoid version jumps in zero-downtime upgrades

261e4e60 · Katrin Leinweber · Marcia Ramos · f4c12321 · 261e4e60
Commit 261e4e60 authored Jun 17, 2021 by Katrin Leinweber Committed by Marcia Ramos Jun 17, 2021
Hide whitespace changes
Inline Side-by-side

Showing with 3 additions and 3 deletions

doc/update/index.md doc/update/index.md +3 -3

No files found.
--- a/doc/update/index.md
+++ b/doc/update/index.md
@@ -186,9 +186,9 @@ migration](../integration/elasticsearch.md#retry-a-halted-migration).
 ## Upgrade paths
-You can generally upgrade through multiple GitLab versions in one go,
+Upgrading across multiple GitLab versions in one go is *only possible with downtime*.
-although this is discouraged for [zero downtime upgrades](#upgrading-without-downtime) and
+The following examples assume a downtime upgrade.
-sometimes this can cause issues.
+See the section below for [zero downtime upgrades](#upgrading-without-downtime).
 Find where your version sits in the upgrade path below, and upgrade GitLab
 accordingly, while also consulting the