Skip to content

Commit c25c008

Browse files
committed
clarifying guidance arround upgrade from version prior to v4.10
1 parent 4c01e47 commit c25c008

File tree

2 files changed

+11
-9
lines changed

2 files changed

+11
-9
lines changed

modules/nw-metalLB-basic-upgrade-operator.adoc

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -45,7 +45,7 @@ metallb 33m
4545
+
4646
[NOTE]
4747
====
48-
When installing the latest {product-version} version of the MetalLB Operator, you must install the Operator to the same namespace it was previously installed to.
48+
When installing the latest {product-version} version of the MetalLB Operator, you must install the Operator to the same namespace it was previously installed to.
4949
====
5050

5151
. Verify the upgraded version of the Operator is now the {product-version} version.
@@ -56,9 +56,9 @@ $ oc get csv -n metallb-system
5656
----
5757
+
5858
.Example output
59-
[source,terminal]
59+
[source,terminal,subs="attributes+"]
6060
----
6161
NAME DISPLAY VERSION REPLACES PHASE
62-
metallb-operator.4.12.0-202207051316 MetalLB Operator 4.12.0-202207051316 Succeeded
62+
metallb-operator.4.{product-version}.0-202207051316 MetalLB Operator 4.{product-version}.0-202207051316 Succeeded
6363
----
6464

networking/metallb/metallb-upgrading-operator.adoc

Lines changed: 8 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -1,31 +1,33 @@
11
:_content-type: ASSEMBLY
22
[id="metallb-upgrading-operator"]
3-
= Upgrading the MetalLB Operator
3+
= Upgrading the MetalLB
44
include::_attributes/common-attributes.adoc[]
55
:context: metallb-upgrading-operator
66

77
toc::[]
88

9-
The automatic upgrade procedure does not work as expected from {product-title} 4.10 and earlier. A summary of the upgrade procedure is as follows:
9+
If you are currently running version 4.10 or an earlier version of the MetalLB Operator, please note that automatic updates to any version later than 4.10 do not work. Upgrading to a newer version from any version of the MetalLB Operator that is 4.11 or later is successful. For example, upgrading from version 4.12 to version 4.13 will occur smoothly.
1010

11-
. Delete the previously installed Operator version for example 4.10. Ensure that the namespace and the `metallb` custom resource are not removed.
11+
A summary of the upgrade procedure for the MetalLB Operator from 4.10 and earlier is as follows:
1212

13-
. Install the 4.11 version of the Operator using the CLI. Install the 4.11 version of the Operator in the same namespace that the previously installed Operator version was installed to.
13+
. Delete the installed MetalLB Operator version for example 4.10. Ensure that the namespace and the `metallb` custom resource are not removed.
14+
15+
. Using the CLI, install the MetalLB Operator {product-version} in the same namespace where the previous version of the MetalLB Operator was installed.
1416

1517
[NOTE]
1618
====
1719
This procedure does not apply to automatic z-stream updates of the MetalLB Operator, which follow the standard straightforward method.
1820
====
1921

20-
For detailed steps to upgrade the Operator, see the guidance that follows.
22+
For detailed steps to upgrade the MetalLB Operator from 4.10 and earlier, see the guidance that follows.
2123

2224
//Delete metallb using web console
2325
include::modules/olm-deleting-metallb-operators-from-a-cluster-using-web-console.adoc[leveloffset=+1]
2426

2527
//Delete metallb using cli
2628
include::modules/olm-deleting-metallb-operators-from-a-cluster-using-cli.adoc[leveloffset=+1]
2729

28-
//Upgrade the Operator
30+
//Upgrade the MetalLB
2931
include::modules/nw-metalLB-basic-upgrade-operator.adoc[leveloffset=+1]
3032

3133
[id="additional-resources"]

0 commit comments

Comments
 (0)