Merge pull request #59223 from obrown1205/eus_layered

OSDOCS#3634: Adding eus-to-eus info for layered products and OLM operators

Author: bscott-rh

modules/updating-eus-to-eus-layered-products.adoc

@@ -0,0 +1,44 @@
+// Module included in the following assemblies:
+//
+// * updating/preparing-eus-eus-upgrade.adoc
+
+:_content-type: PROCEDURE
+[id="updating-eus-to-eus-olm-operators_{context}"]
+= EUS-to-EUS update for layered products and Operators installed through Operator Lifecycle Manager 
+
+In addition to the EUS-to-EUS update steps mentioned for the web console and CLI, there are additional steps to consider when performing EUS-to-EUS updates for clusters with the following:
+
+* Layered products 
+* Operators installed through Operator Lifecycle Manager (OLM)
+
+.What is a layered product?
+
+Layered products refer to products that are made of multiple underlying products that are intended to be used together and cannot be broken into individual subscriptions. For examples of layered {product-title} products, see link:https://access.redhat.com/support/policy/updates/openshift/#layered[Layered Offering On OpenShift].
+
+As you perform an EUS-to-EUS update for the clusters of layered products and those of Operators that have been installed through OLM, you must complete the following:
+
+. Ensure that all of your Operators previously installed through OLM are updated to their latest version in their latest channel. Updating the Operators ensures that they have a valid update path when the default OperatorHub catalogs switch from the current minor version to the next during a cluster update. For information on how to update your Operators, see "Preparing for an Operator update" in "Additional resources".
+
+. Confirm the cluster version compatibility between the current and intended Operator versions. You can verify which versions your OLM Operators are compatible with by using the link:https://access.redhat.com/labs/ocpouic/?operator=logging&&ocp_versions=4.10,4.11,4.12[Red Hat {product-title} Operator Update Information Checker].
+
+As an example, here are the steps to perform an EUS-to-EUS update from <4.y> to <4.y+2> for OpenShift Data Foundation (ODF). This can be done through the CLI or web console. For information on how to update clusters through your desired interface, see _EUS-to-EUS update using the web console_ and "EUS-to-EUS update using the CLI" in "Additional resources".
+
+.Example workflow
+. Pause the worker machine pools.
+. Upgrade OpenShift <4.y> -> OpenShift <4.y+1>.
+. Upgrade ODF <4.y> -> ODF <4.y+1>.
+. Upgrade OpenShift <4.y+1> -> OpenShift <4.y+2>.
+. Upgrade to ODF <4.y+2>.
+. Unpause the worker machine pools.
+
+[NOTE]
+====
+The upgrade to ODF <4.y+2> can happen before or after worker machine pools have been unpaused.
+====
+
+
+
+
+
+
+

updating/preparing-eus-eus-upgrade.adoc

@@ -46,3 +46,12 @@ include::modules/updating-eus-to-eus-upgrade-cli.adoc[leveloffset=+2]
 .Additional resources
 
 * xref:../operators/admin/olm-upgrading-operators.adoc#olm-upgrading-operators[Updating installed Operators]
+
+include::modules/updating-eus-to-eus-layered-products.adoc[leveloffset=+2]
+[role="_additional-resources"]
+[id="additional-resources_updating-eus-to-eus-layered-products"]
+.Additional resources
+
+* xref:../operators/admin/olm-upgrading-operators.adoc#olm-preparing-upgrade_olm-upgrading-operators[Preparing for an Operator update]
+* xref:../updating/preparing-eus-eus-upgrade.adoc#updating-eus-to-eus-upgrade-console_eus-to-eus-upgrade[EUS-to-EUS update using the web console]
+* xref:../updating/preparing-eus-eus-upgrade.adoc#updating-eus-to-eus-upgrade-cli_eus-to-eus-upgrade[EUS-to-EUS update using the CLI]