Merge pull request #55183 from jneczypor/OSDOCS4654-HideBackupContent

OSDOCS:4654-Hide Backup Content

Author: kelbrown20

modules/rosa-policy-incident.adoc

@@ -41,49 +41,46 @@ The following activities can trigger notifications:
 - Upgrade scheduling
 
 [id="rosa-policy-backup-recovery-sts_{context}"]
-== Backup and recovery for ROSA clusters with STS
+== Infrastructure and data resiliency
+Customers are responsible for taking regular backups of their data and should deploy multi-AZ clusters with workloads that follow Kubernetes best practices to ensure high availability within a region. If an entire cloud region is unavailable, customers must install a new cluster in a different region and restore their apps using their backup data.
 
-There is no backup method available for ROSA clusters with STS.
+There is no Red Hat-provided backup method available for ROSA clusters with STS. Red Hat does not commit to any Recovery Point Objective (RPO) or Recovery Time Objective (RTO).
 
-[id="backup-recovery_{context}"]
-== Backup and recovery
-All Red Hat OpenShift Service on AWS cluster metadata from OpenShift Cluster Manager is securely backed up by Red Hat. The following table outlines backup and recovery strategies:
+//Note: The following content will be used again in the future (per OSDOCS:4654)
+//[id="backup-recovery_{context}"]
+//== Backup and recovery
+//All Red Hat OpenShift Service on AWS cluster metadata from OpenShift Cluster Manager is securely backed up by Red Hat. The following table outlines backup and recovery strategies:
 
 //Verify if the corresponding tables in rosa-sdpolicy-platform.adoc and policy-incident.adoc also need to be updated. 
 
-[cols= "3a,2a,2a,3a",options="header"]
+//[cols= "3a,2a,2a,3a",options="header"]
 
-|===
-|Component
-|Snapshot frequency
-|Retention
-|Notes
+//|===
+//|Component
+//|Snapshot frequency
+//|Retention
+//|Notes
 
-.2+|Full object store backup, all cluster persistent volumes (PVs)
-|Daily
-|7 days
-.2+|This is a full backup of all Kubernetes objects like etcd, as well as all PVs in the cluster.
+//.2+|Full object store backup, all cluster persistent volumes (PVs)
+//|Daily
+//|7 days
+//.2+|This is a full backup of all Kubernetes objects like etcd, as well as all PVs in the cluster.
 
-|Weekly
-|30 days
+//|Weekly
+//|30 days
 
 
-|Full object store backup
-|Hourly
-|24 hour
-|This is a full backup of all Kubernetes objects like etcd. No PVs are backed up in this backup schedule.
+//|Full object store backup
+//|Hourly
+//|24 hour
+//|This is a full backup of all Kubernetes objects like etcd. No PVs are backed up in this backup schedule.
 
-|Node root volume
-|Never
-|N/A
-|Nodes are considered to be short-term. Nothing critical should be stored on a node's root volume.
+//|Node root volume
+//|Never
+//|N/A
+//|Nodes are considered to be short-term. Nothing critical should be stored on a node's root volume.
 
-|===
-
-* Red Hat does not commit to any Recovery Point Objective (RPO) or Recovery Time Objective (RTO).
-* Customers are responsible for taking regular backups of their data
-* Customers should deploy multi-AZ clusters with workloads that follow Kubernetes best practices to ensure high availability within a region.
-* If an entire cloud region is unavailable, customers must install a new cluster in a different region and restore their apps using their backup data.
+//|===
 
 [id="rosa-policy-cluster-capacity_{context}"]
 == Cluster capacity