From ef94e79f442a68e54d7e9fbc36f4d85ed5da59ff Mon Sep 17 00:00:00 2001 From: Giovanni Geraci Date: Wed, 4 Jun 2025 16:58:30 +0200 Subject: [PATCH 1/2] Fixing small typo in operator-upgrade.adoc --- modules/operator-upgrade.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/modules/operator-upgrade.adoc b/modules/operator-upgrade.adoc index 85cbc175e..1561a51b2 100644 --- a/modules/operator-upgrade.adoc +++ b/modules/operator-upgrade.adoc @@ -18,7 +18,7 @@ When the {productname} Operator is installed by Operator Lifecycle Manager, it m The standard approach for upgrading installed Operators on {ocp} is documented at link:https://docs.openshift.com/container-platform/{ocp-y}/operators/admin/olm-upgrading-operators.html[Upgrading installed Operators]. -In general, {productname} supports upgrades from a prior (N-1) minor version only. For example, upgrading directly from {productname} 3.5 to the latest version of {producty-min} is not supported. Instead, users would have to upgrade as follows: +In general, {productname} supports upgrades from a prior (N-1) minor version only. For example, upgrading directly from {productname} 3.5 to the latest version of {productmin} is not supported. Instead, users would have to upgrade as follows: . 3.9.z -> 3.10.z . 3.10.z -> 3.11.z From 4193e5b305a0e4988f95612f68c2eed644633f0c Mon Sep 17 00:00:00 2001 From: Giovanni Geraci Date: Wed, 4 Jun 2025 17:36:02 +0200 Subject: [PATCH 2/2] Replace productmin with producty --- modules/operator-upgrade.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/modules/operator-upgrade.adoc b/modules/operator-upgrade.adoc index 1561a51b2..3b6869510 100644 --- a/modules/operator-upgrade.adoc +++ b/modules/operator-upgrade.adoc @@ -18,7 +18,7 @@ When the {productname} Operator is installed by Operator Lifecycle Manager, it m The standard approach for upgrading installed Operators on {ocp} is documented at link:https://docs.openshift.com/container-platform/{ocp-y}/operators/admin/olm-upgrading-operators.html[Upgrading installed Operators]. -In general, {productname} supports upgrades from a prior (N-1) minor version only. For example, upgrading directly from {productname} 3.5 to the latest version of {productmin} is not supported. Instead, users would have to upgrade as follows: +In general, {productname} supports upgrades from a prior (N-1) minor version only. For example, upgrading directly from {productname} 3.5 to the latest version of {producty} is not supported. Instead, users would have to upgrade as follows: . 3.9.z -> 3.10.z . 3.10.z -> 3.11.z