Commit 261e4e60 authored by Katrin Leinweber's avatar Katrin Leinweber Committed by Marcia Ramos

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

parent f4c12321
......@@ -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,
although this is discouraged for [zero downtime upgrades](#upgrading-without-downtime) and
sometimes this can cause issues.
Upgrading across multiple GitLab versions in one go is *only possible with downtime*.
The following examples assume a downtime upgrade.
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
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment