Skip to content

Commit 69beef8

Browse files
committed
QE
1 parent 6d32cd2 commit 69beef8

File tree

2 files changed

+28
-7
lines changed

2 files changed

+28
-7
lines changed

modules/virt-about-eus-updates.adoc

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -6,9 +6,9 @@
66
[id="virt-about-eus-updates_{context}"]
77
= About EUS-to-EUS updates
88

9-
Every even-numbered minor version of {product-title}, including 4.10 and 4.12, is an Extended Update Support (EUS) version. However, because Kubernetes design mandates serial minor version updates, you cannot directly update from one EUS version to the next. You must first update to the odd-numbered minor version before you can proceed to the target EUS version.
9+
Every even-numbered minor version of {product-title}, including 4.10 and 4.12, is an Extended Update Support (EUS) version. However, because Kubernetes design mandates serial minor version updates, you cannot directly update from one EUS version to the next. You must first update to the each z-stream release of the odd-numbered minor version before you can proceed to the target EUS version.
1010

11-
When performing an EUS-to-EUS update, you must:
11+
Before beginning an EUS-to-EUS update, you must:
1212

1313
* Pause worker nodes' machine config pools before you start an EUS-to-EUS update so that the workers are not rebooted twice.
1414

modules/virt-preventing-workload-updates-during-eus-update.adoc

Lines changed: 26 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@
66
[id="virt-preventing-workload-updates-during-eus-update_{context}"]
77
= Preventing workload updates during an EUS-to-EUS update
88

9-
Before you begin to update from one Extended Update Support (EUS) version to the next, you must manually disable automatic workload updates.
9+
When you update from one Extended Update Support (EUS) version to the next, you must manually disable automatic workload updates to prevent {VirtProductName} from migrating or evicting workloads during the update process.
1010

1111
.Prerequisites
1212

@@ -42,7 +42,7 @@ hyperconverged.hco.kubevirt.io/kubevirt-hyperconverged patched
4242
+
4343
[source,terminal]
4444
----
45-
$ kubectl get hco kubevirt-hyperconverged -n openshift-cnv -o json | jq ".status.conditions"
45+
$ oc get hco kubevirt-hyperconverged -n openshift-cnv -o json | jq ".status.conditions"
4646
----
4747
+
4848
.Example output
@@ -129,14 +129,35 @@ $ oc get csv -n openshift-cnv
129129
If you used the *Manual* approval strategy, you must approve the update in the web console. For more details, refer to the "Manually approving a pending Operator update" section.
130130
====
131131

132-
. After you confirm that {VirtProductName} successfully updated to the non-EUS version, wait until the `HyperConverged` Operator has the `Upgradeable` status before you perform the next update. Enter the following command and monitor the output:
132+
. Confirm that {VirtProductName} successfully updated to the non-EUS version by running the following command:
133133
+
134134
[source,terminal]
135135
----
136-
$ kubectl get hco kubevirt-hyperconverged -n openshift-cnv -o json | jq ".status.conditions"
136+
$ oc get hco kubevirt-hyperconverged -n openshift-cnv -o json | jq ".status.versions"
137+
----
138+
+
139+
.Example output
140+
[source,terminal]
141+
----
142+
[
143+
{
144+
"name": "operator",
145+
"version": "{HCOVersion}"
146+
}
147+
]
148+
----
149+
150+
. Wait until the `HyperConverged` Operator has the `Upgradeable` status before you perform the next update. Enter the following command and monitor the output:
151+
+
152+
[source,terminal]
153+
----
154+
$ oc get hco kubevirt-hyperconverged -n openshift-cnv -o json | jq ".status.conditions"
137155
----
138156

139-
. Update {product-title} and {VirtProductName} to the target EUS version, monitoring as in the preceding steps to ensure that the updates succeed.
157+
. Continue to update your cluster and {VirtProductName} as described in the preceding steps, monitoring to ensure that the updates succeed.
158+
.. Update {product-title} and, subsequently, {VirtProductName}, until you install the latest z-stream release of the non-EUS minor version. Ensure that you update both {product-title} and {VirtProductName} to this version.
159+
.. Update {product-title} to the target EUS version.
160+
.. Update {VirtProductName} to the target EUS version.
140161

141162
. Restore the workload update methods configuration that you backed up:
142163
+

0 commit comments

Comments
 (0)