Update versions under Upgrade path section

tigera · Nov 20, 2024 · b9fc3b4 · b9fc3b4
1 parent 895c5bd
commit b9fc3b4
Show file tree

Hide file tree

Showing 6 changed files with 12 additions and 12 deletions.
diff --git a/...enterprise/getting-started/upgrading/upgrading-enterprise/openshift-upgrade.mdx b/...enterprise/getting-started/upgrading/upgrading-enterprise/openshift-upgrade.mdx
@@ -15,9 +15,9 @@ All upgrades in $[prodname] are free with a valid license.
 
 ## Upgrades paths
 
-You can upgrade your cluster to a maximum of **two releases** from your existing version. For example, if you are on version 3.6, you can upgrade to 3.7, or you can upgrade directly to 3.8. However, you cannot upgrade beyond **two releases**; upgrading from 3.6 to 3.9 (three releases) is not supported.
+You can upgrade your cluster to a maximum of **two releases** from your existing version. For example, if you are on version 3.16, you can upgrade to 3.17, or you can upgrade directly to 3.18. However, you cannot upgrade beyond **two releases**; upgrading from 3.16 to 3.19 (three releases) is not supported.
 
-If you are several versions behind where you want to be, you must go through each group of two releases to get there. For example, if you are on version 3.6, and you want to get to 3.10, you can upgrade to 3.8, then upgrade from 3.8 directly to 3.10.
+If you are several versions behind where you want to be, you must go through each group of two releases to get there. For example, if you are on version 3.16, and you want to get to 3.20, you can upgrade to 3.18, then upgrade from 3.18 directly to 3.20.
 
 :::note
 

diff --git a/...rsion-3.17/getting-started/upgrading/upgrading-enterprise/openshift-upgrade.mdx b/...rsion-3.17/getting-started/upgrading/upgrading-enterprise/openshift-upgrade.mdx
@@ -15,9 +15,9 @@ All upgrades in $[prodname] are free with a valid license.
 
 ## Upgrades paths
 
-You can upgrade your cluster to a maximum of **two releases** from your existing version. For example, if you are on version 3.6, you can upgrade to 3.7, or you can upgrade directly to 3.8. However, you cannot upgrade beyond **two releases**; upgrading from 3.6 to 3.9 (three releases) is not supported.
+You can upgrade your cluster to a maximum of **two releases** from your existing version. For example, if you are on version 3.14, you can upgrade to 3.15, or you can upgrade directly to 3.16. However, you cannot upgrade beyond **two releases**; upgrading from 3.14 to 3.17 (three releases) is not supported.
 
-If you are several versions behind where you want to be, you must go through each group of two releases to get there. For example, if you are on version 3.6, and you want to get to 3.10, you can upgrade to 3.8, then upgrade from 3.8 directly to 3.10.
+If you are several versions behind where you want to be, you must go through each group of two releases to get there. For example, if you are on version 3.14, and you want to get to 3.17, you can upgrade to 3.16, then upgrade from 3.16 directly to 3.17.
 
 :::note
 

diff --git a/...ion-3.18-2/getting-started/upgrading/upgrading-enterprise/openshift-upgrade.mdx b/...ion-3.18-2/getting-started/upgrading/upgrading-enterprise/openshift-upgrade.mdx
@@ -15,9 +15,9 @@ All upgrades in $[prodname] are free with a valid license.
 
 ## Upgrades paths
 
-You can upgrade your cluster to a maximum of **two releases** from your existing version. For example, if you are on version 3.6, you can upgrade to 3.7, or you can upgrade directly to 3.8. However, you cannot upgrade beyond **two releases**; upgrading from 3.6 to 3.9 (three releases) is not supported.
+You can upgrade your cluster to a maximum of **two releases** from your existing version. For example, if you are on version 3.15, you can upgrade to 3.16, or you can upgrade directly to 3.17. However, you cannot upgrade beyond **two releases**; upgrading from 3.15 to 3.18 (three releases) is not supported.
 
-If you are several versions behind where you want to be, you must go through each group of two releases to get there. For example, if you are on version 3.6, and you want to get to 3.10, you can upgrade to 3.8, then upgrade from 3.8 directly to 3.10.
+If you are several versions behind where you want to be, you must go through each group of two releases to get there. For example, if you are on version 3.15, and you want to get to 3.18, you can upgrade to 3.17, then upgrade from 3.17 directly to 3.18.
 
 :::note
 

diff --git a/...ion-3.19-2/getting-started/upgrading/upgrading-enterprise/openshift-upgrade.mdx b/...ion-3.19-2/getting-started/upgrading/upgrading-enterprise/openshift-upgrade.mdx
@@ -15,9 +15,9 @@ All upgrades in $[prodname] are free with a valid license.
 
 ## Upgrades paths
 
-You can upgrade your cluster to a maximum of **two releases** from your existing version. For example, if you are on version 3.6, you can upgrade to 3.7, or you can upgrade directly to 3.8. However, you cannot upgrade beyond **two releases**; upgrading from 3.6 to 3.9 (three releases) is not supported.
+You can upgrade your cluster to a maximum of **two releases** from your existing version. For example, if you are on version 3.15, you can upgrade to 3.16, or you can upgrade directly to 3.17. However, you cannot upgrade beyond **two releases**; upgrading from 3.15 to 3.18 (three releases) is not supported.
 
-If you are several versions behind where you want to be, you must go through each group of two releases to get there. For example, if you are on version 3.6, and you want to get to 3.10, you can upgrade to 3.8, then upgrade from 3.8 directly to 3.10.
+If you are several versions behind where you want to be, you must go through each group of two releases to get there. For example, if you are on version 3.16, and you want to get to 3.19, you can upgrade to 3.18, then upgrade from 3.18 directly to 3.19.
 
 :::note
 

diff --git a/...ion-3.20-1/getting-started/upgrading/upgrading-enterprise/openshift-upgrade.mdx b/...ion-3.20-1/getting-started/upgrading/upgrading-enterprise/openshift-upgrade.mdx
@@ -15,9 +15,9 @@ All upgrades in $[prodname] are free with a valid license.
 
 ## Upgrades paths
 
-You can upgrade your cluster to a maximum of **two releases** from your existing version. For example, if you are on version 3.6, you can upgrade to 3.7, or you can upgrade directly to 3.8. However, you cannot upgrade beyond **two releases**; upgrading from 3.6 to 3.9 (three releases) is not supported.
+You can upgrade your cluster to a maximum of **two releases** from your existing version. For example, if you are on version 3.16, you can upgrade to 3.17, or you can upgrade directly to 3.18. However, you cannot upgrade beyond **two releases**; upgrading from 3.16 to 3.19 (three releases) is not supported.
 
-If you are several versions behind where you want to be, you must go through each group of two releases to get there. For example, if you are on version 3.6, and you want to get to 3.10, you can upgrade to 3.8, then upgrade from 3.8 directly to 3.10.
+If you are several versions behind where you want to be, you must go through each group of two releases to get there. For example, if you are on version 3.16, and you want to get to 3.20, you can upgrade to 3.18, then upgrade from 3.18 directly to 3.20.
 
 :::note
 

diff --git a/...ion-3.20-2/getting-started/upgrading/upgrading-enterprise/openshift-upgrade.mdx b/...ion-3.20-2/getting-started/upgrading/upgrading-enterprise/openshift-upgrade.mdx
@@ -15,9 +15,9 @@ All upgrades in $[prodname] are free with a valid license.
 
 ## Upgrades paths
 
-You can upgrade your cluster to a maximum of **two releases** from your existing version. For example, if you are on version 3.6, you can upgrade to 3.7, or you can upgrade directly to 3.8. However, you cannot upgrade beyond **two releases**; upgrading from 3.6 to 3.9 (three releases) is not supported.
+You can upgrade your cluster to a maximum of **two releases** from your existing version. For example, if you are on version 3.16, you can upgrade to 3.17, or you can upgrade directly to 3.18. However, you cannot upgrade beyond **two releases**; upgrading from 3.16 to 3.19 (three releases) is not supported.
 
-If you are several versions behind where you want to be, you must go through each group of two releases to get there. For example, if you are on version 3.6, and you want to get to 3.10, you can upgrade to 3.8, then upgrade from 3.8 directly to 3.10.
+If you are several versions behind where you want to be, you must go through each group of two releases to get there. For example, if you are on version 3.16, and you want to get to 3.20, you can upgrade to 3.18, then upgrade from 3.18 directly to 3.20.
 
 :::note