Merge pull request #44691 from sayjadha/JIRA-OSDOCS3265

JIRA-OSDOCS3265: Updated the release management content for ROSA

Author: ahardin-rh

modules/rosa-policy-change-management.adoc

@@ -62,6 +62,11 @@ OpenShift Container Platform software and the underlying immutable Red Hat CoreO
 [id="rosa-policy-release-management_{context}"]
 == Release management
 
-ROSA clusters can be configured for automatic upgrades on a schedule. Alternatively, you can perform manual upgrades using the `rosa` CLI. For more details, see the link:https://access.redhat.com/support/policy/updates/openshift/dedicated[Life Cycle policy].
+Red Hat does not automatically upgrade your clusters. You can schedule to upgrade the clusters at regular intervals (recurring upgrade) or just once (individual upgrade) using the {cluster-manager} web console. Red Hat might forcefully upgrade a cluster to a new z-stream version only if the cluster is affected by a critical impact CVE.
 
-Customers can review the history of all cluster upgrade events in their {cluster-manager} web console on the Events tab.
+[NOTE]
+====
+ROSA clusters that use the AWS Security Token Service (STS) need an interruption between upgrades to ensure that the STS roles and policies are updated. Therefore, you cannot schedule recurring upgrades on ROSA clusters with STS.
+====
+
+You can review the history of all cluster upgrade events in the {cluster-manager} web console. For more information about releases, see the link:https://access.redhat.com/support/policy/updates/openshift/dedicated[Life Cycle policy].