You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: modules/updating-eus-to-eus-upgrade.adoc
+15-18Lines changed: 15 additions & 18 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,17 +6,14 @@
6
6
[id="updating-eus-to-eus-upgrade_{context}"]
7
7
= EUS-to-EUS update
8
8
9
-
The following procedure pauses all non-master MachineConfigPools and performs updates from {product-title} 4.8 to 4.9 to 4.10, then unpauses the previously paused MachineConfigPools.
9
+
The following procedure pauses all non-master MachineConfigPools and performs updates from {product-title} 4.10 to 4.11 to 4.12, then unpauses the previously paused MachineConfigPools.
10
10
Following this procedure reduces the total update duration and the number of times worker nodes are restarted.
11
11
12
12
.Prerequisites
13
13
14
-
* Review the release notes for {product-title} 4.9 and 4.10
14
+
* Review the release notes for {product-title} 4.11 and 4.12
15
15
* Review the release notes and product lifecycles for any layered products and OLM Operators. Some may require updates either before or during an EUS-to-EUS update.
16
-
* Ensure that you are familiar with version-specific prerequisites, such as link:https://docs.openshift.com/container-platform/4.9/updating/updating-cluster-prepare.html#update-preparing-migrate_updating-cluster-prepare[administrator acknowledgement] that is required prior to updating from {product-title} 4.8 to 4.9.
17
-
* Verify that your cluster is running {product-title} version 4.8.14 or later.
18
-
If your cluster is running a version earlier than {product-title} 4.8.14, you must update to a later 4.8.z version before updating to 4.9.
19
-
The update to 4.8.14 or later is necessary to fulfill the minimum version requirements that must be performed without pausing MachineConfigPools.
16
+
* Ensure that you are familiar with version-specific prerequisites, such as link:https://docs.openshift.com/container-platform/4.12/updating/updating-cluster-prepare.html#update-preparing-migrate_updating-cluster-prepare[administrator acknowledgement] that is required prior to updating from {product-title} 4.11 to 4.12.
20
17
* Verify that MachineConfigPools is unpaused.
21
18
* Update OpenShift CLI `oc` to the target version before each update.
If pools are not unpaused, the cluster is not permitted to update to any future minor versions, and maintenance tasks such as certificate rotation are inhibited. This puts the cluster at risk for future degradation.
138
135
====
139
136
140
-
. Verify that your previously paused pools updated and that your cluster completed the update to version 4.10. Run the following command:
137
+
. Verify that your previously paused pools updated and that your cluster completed the update to version 4.12. Run the following command:
xref:../updating/preparing-eus-eus-upgrade.adoc#preparing-eus-eus-upgrade[Preparing to perform an EUS-to-EUS update]: Due to fundamental Kubernetes design, all {product-title} updates between minor versions must be serialized. You must update from {product-title} 4.9 to 4.10, and then to 4.11. You cannot update from {product-title} 4.8 to 4.10 directly. However, if you want to update between two Extended Update Support (EUS) versions, you can do so by incurring only a single reboot of non-control plane hosts. For more information, see the following:
29
+
xref:../updating/preparing-eus-eus-upgrade.adoc#preparing-eus-eus-upgrade[Preparing to perform an EUS-to-EUS update]: Due to fundamental Kubernetes design, all {product-title} updates between minor versions must be serialized. You must update from {product-title} 4.10 to 4.11, and then to 4.12. You cannot update from {product-title} 4.10 to 4.12 directly. However, if you want to update between two Extended Update Support (EUS) versions, you can do so by incurring only a single reboot of non-control plane hosts. For more information, see the following:
Due to fundamental Kubernetes design, all {product-title} updates between minor versions must be serialized.
10
-
You must update from {product-title} 4.9 to 4.10 and then to 4.11. You cannot update from {product-title} 4.9 to 4.11 directly.
11
-
However, beginning with the update from {product-title} 4.9 to 4.10 to 4.11, administrators who wish to update between two Extended Update Support (EUS) versions can do so incurring only a single reboot of non-control plane hosts.
10
+
You must update from {product-title} 4.10 to 4.11 and then to 4.12. You cannot update from {product-title} 4.10 to 4.12 directly.
11
+
However, beginning with the update from {product-title} 4.10 to 4.11 to 4.12, administrators who wish to update between two Extended Update Support (EUS) versions can do so incurring only a single reboot of non-control plane hosts.
12
12
13
13
There are a number of caveats to consider when attempting an EUS-to-EUS update.
14
14
15
15
* EUS-to-EUS updates are only offered after updates between all versions involved have been made available in `stable` channels.
16
16
* If you encounter issues during or after upgrading to the odd-numbered minor version but before upgrading to the next even-numbered version, then remediation of those issues may require that non-control plane hosts complete the update to the odd-numbered version before moving forward.
17
17
* You can do a partial update by updating the worker or custom pool nodes to accommodate the time it takes for maintenance.
18
18
* You can complete the update process during multiple maintenance windows by pausing at intermediate steps. However, plan to complete the entire update within 60 days. This is critical to ensure that normal cluster automation processes are completed including those associated with certificate rotation.
19
-
* You must be running at least {product-title} 4.8.14 before starting the EUS-to-EUS update procedure. If you do not meet this minimum requirement, update to a later 4.8.z before attempting the EUS-to-EUS update.
20
-
* Support for RHEL7 workers was removed in {product-title} 4.10 and replaced with RHEL8 workers, therefore EUS-to-EUS updates are not available for clusters with RHEL7 workers.
21
-
* Node components are not updated to {product-title} 4.9. Do not expect all features and bugs fixed in {product-title} 4.9 to be made available until you complete the update to {product-title} 4.10 and enable all MachineConfigPools to update.
19
+
* Support for RHEL7 workers was removed in {product-title} 4.10 and replaced with RHEL8 workers, therefore EUS-to-EUS updates are not available for clusters with RHEL7 workers.
20
+
+
21
+
Verify that no RHEL7 workers are present in the 4.10 cluster before performing an EUS-to-EUS upgrade to 4.12. You must replace RHEL7 workers with RHEL8 or RHCOS workers before upgrading to {product-title} 4.12. Red Hat does not support in-place RHEL7 to RHEL8 updates for RHEL workers; those hosts must be replaced with a clean operating system install.
22
+
23
+
* Node components are not updated to {product-title} 4.11. Do not expect all features and bugs fixed in {product-title} 4.11 to be made available until you complete the update to {product-title} 4.12 and enable all MachineConfigPools to update.
22
24
* All the clusters might update using EUS channels for a conventional update without pools paused, but only clusters with non control-plane `MachineConfigPools` objects can do EUS-to-EUS update with pools paused.
0 commit comments