Merge pull request #74729 from mletalie/OSDOCS-10170.1

[OSDOCS-10170]:Remove obsolete information about upgrading ROSA cluster sections

Author: EricPonvelle

_topic_maps/_topic_map_rosa.yml

@@ -680,9 +680,6 @@ Name: Upgrading
 Dir: upgrading
 Distros: openshift-rosa
 Topics:
-- Name: Preparing to upgrade ROSA to 4.9
-  File: rosa-upgrading-cluster-prepare
-  Distros: openshift-rosa
 - Name: Upgrading ROSA with STS
   File: rosa-upgrading-sts
 - Name: Upgrading ROSA
@@ -1907,6 +1904,10 @@ Topics:
     File: virt-backing-up-vms
   - Name: Restoring virtual machines
     File: virt-restoring-vms
-#  - Name: Collecting OKD Virtualization data for community report
-#    File: virt-collecting-virt-data
-#    Distros: openshift-origin
+#  - Name: Removed topics (Placeholder for topics removed from topic map)
+#    Dir: Removed_topics
+#    Topics:
+#    - Name: Collecting OKD Virtualization data for community report
+#      File: virt-collecting-virt-data
+#    - Name: Preparing to upgrade ROSA to 4.9
+#      File: rosa-upgrading-cluster-prepare

modules/rosa-upgrading-automatic-ocm.adoc

@@ -18,7 +18,6 @@ You can schedule recurring, automatic upgrades for z-stream patch versions for y
 . Select a preferred day of the week and start time for the upgrade, when updates are available.
 . Provide an administrator’s acknowledgment and click *Approve and continue*. {cluster-manager} does not start scheduled y-stream updates for minor versions without receiving an administrator’s acknowledgment.
 +
-For information about administrator acknowledgment, see xref:./../upgrading/rosa-upgrading-cluster-prepare.adoc#upgrade-49-acknowledgement_rosa-updating-cluster-prepare[Administrator acknowledgment when upgrading to OpenShift 4.9].
 . In the *Node draining* pane, select a grace period interval from the list. The grace period enables the nodes to gracefully drain before forcing the pod eviction. The default is *1 hour*.
 . In the *Update strategy* pane, click *Save* to apply your update strategy.
 +

modules/rosa-upgrading-cli-tutorial.adoc

@@ -26,9 +26,6 @@ This method schedules the cluster for an immediate upgrade, if a more recent ver
 .Prerequisites
 
 * You have installed and configured the latest ROSA CLI on your installation host.
-ifdef::sts[]
-* If you are upgrading your cluster from 4.7 to 4.8, you have upgraded the AWS Identity and Access Management (IAM) account-wide roles and policies to version 4.8. You have also updated the `cloudcredential.openshift.io/upgradeable-to` annotation in the `CloudCredential` custom resource.
-endif::sts[]
 
 .Procedure
 

modules/rosa-upgrading-manual-ocm.adoc

@@ -17,12 +17,6 @@ that uses the AWS Security Token Service (STS)
 endif::sts[]
 manually one time by using {cluster-manager} console.
 
-ifdef::sts[]
-.Prerequisites
-
-* If you are upgrading your cluster from 4.7 to 4.8, you have upgraded the AWS Identity and Access Management (IAM) account-wide roles and policies to version 4.8. You have also updated the `cloudcredential.openshift.io/upgradeable-to` annotation in the `CloudCredential` custom resource. For more information, see _Preparing an upgrade from 4.7 to 4.8_.
-endif::sts[]
-
 .Procedure
 
 . Log in to {cluster-manager-url}.
@@ -32,7 +26,6 @@ endif::sts[]
 . Select the version you want to upgrade your cluster to. Recommended cluster upgrades appear in the UI.
 . If you select an update version that requires approval, provide an administrator’s acknowledgment and click *Approve and continue*.
 +
-For information about administrator acknowledgment, see xref:./../upgrading/rosa-upgrading-cluster-prepare.adoc#upgrade-49-acknowledgement_rosa-updating-cluster-prepare[Administrator acknowledgment when upgrading to OpenShift 4.9].
 . In the *Node draining* pane, select a grace period interval from the list. The grace period enables the nodes to gracefully drain before forcing the pod eviction. The default is *1 hour*.
 +
 [NOTE]