Merge pull request #84100 from xJustin/OSDOCS-12439-HCP-follow-up

OSDOCS-12439 HCP branch follow up

Author: EricPonvelle

_topic_maps/_topic_map_rosa_hcp.yml

@@ -40,6 +40,10 @@ Topics:
   Dir: rosa_policy_service_definition
   Distros: openshift-rosa-hcp
   Topics:
+  - Name: About availability for ROSA
+    File: rosa-policy-understand-availability
+  - Name: Overview of responsibilities for ROSA
+    File: rosa-policy-responsibility-matrix
   - Name: ROSA with HCP service definition
     File: rosa-hcp-service-definition
   - Name: ROSA with HCP instance types
@@ -48,6 +52,8 @@ Topics:
     File: rosa-hcp-life-cycle
   - Name: SRE and service account access
     File: rosa-sre-access
+  - Name: Understanding security for ROSA
+    File: rosa-policy-process-security
 ---
 Name: Learning about ROSA
 Dir: rosa_learning

modules/rosa-policy-failure-points.adoc

@@ -33,6 +33,7 @@ Worker nodes are the virtual machines that contain your application pods. By def
 When accounting for possible node failures, it is also important to understand how storage is affected. EFS volumes are not affected by node failure. However, EBS volumes are not accessible if they are connected to a node that fails.
 ====
 
+ifndef::openshift-rosa-hcp[]
 [id="rosa-policy-container-cluster-failure_{context}"]
 == Cluster failure
 Single-AZ ROSA clusters have at least three control plane and two infrastructure nodes in the same availability zone (AZ) in the private subnet.
@@ -42,6 +43,7 @@ Multi-AZ ROSA clusters have at least three control plane nodes and three infrast
 In the event of a complete control plane outage, the OpenShift APIs will not function, and existing worker node pods are unaffected. However, if there is also a pod or node outage at the same time, the control planes must recover before new pods or nodes can be added or scheduled.
 
 All services running on infrastructure nodes are configured by Red{nbsp}Hat to be highly available and distributed across infrastructure nodes. In case of a complete infrastructure outage, these services are unavailable until these nodes have been recovered.
+endif::openshift-rosa-hcp[]
 
 [id="rosa-policy-container-zone-failure_{context}"]
 == Zone failure

rosa_architecture/rosa_policy_service_definition/rosa-policy-process-security.adoc

@@ -28,4 +28,9 @@ include::modules/rosa-policy-security-regulation-compliance.adoc[leveloffset=+1]
 
 * For more information about customer or shared responsibilities, see the xref:../../rosa_architecture/rosa_policy_service_definition/rosa-policy-responsibility-matrix.adoc#rosa-policy-responsibilities_rosa-policy-responsibility-matrix[ROSA Responsibilities] document.
 
+ifndef::openshift-rosa-hcp[]
 * For more information about ROSA and its components, see the xref:../../rosa_architecture/rosa_policy_service_definition/rosa-service-definition.adoc#rosa-service-definition[ROSA Service Definition].
+endif::openshift-rosa-hcp[]
+ifdef::openshift-rosa-hcp[]
+* For more information about ROSA and its components, see the xref:../../rosa_architecture/rosa_policy_service_definition/rosa-hcp-service-definition.adoc#rosa-hcp-service-definition[ROSA with HCP Service Definition].
+endif::openshift-rosa-hcp[]

rosa_architecture/rosa_policy_service_definition/rosa-policy-responsibility-matrix.adoc

@@ -10,10 +10,13 @@ This documentation outlines Red{nbsp}Hat, Amazon Web Services (AWS), and custome
 
 include::modules/rosa-policy-responsibilities.adoc[leveloffset=+1]
 
+ifndef::openshift-rosa-hcp[]
 [role="_additional-resources"]
 .Additional resources
 
 * xref:../../rosa_planning/rosa-sts-aws-prereqs.adoc#osd-aws-privatelink-firewall-prerequisites_rosa-sts-aws-prereqs[AWS firewall prerequisites]
+endif::openshift-rosa-hcp[]
+
 
 
 include::modules/rosa-policy-shared-responsibility.adoc[leveloffset=+1]
@@ -29,10 +32,12 @@ include::modules/managed-cluster-notification-policy.adoc[leveloffset=+2]
 include::modules/rosa-policy-incident.adoc[leveloffset=+1]
 include::modules/rosa-policy-change-management.adoc[leveloffset=+1]
 
+ifndef::openshift-rosa-hcp[]
 [role="_additional-resources"]
 .Additional resources
 
 * xref:../../rosa_planning/rosa-sts-aws-prereqs.adoc#osd-aws-privatelink-firewall-prerequisites_rosa-sts-aws-prereqs[AWS firewall prerequisites]
+endif::openshift-rosa-hcp[]
 
 include::modules/rosa-policy-security-and-compliance.adoc[leveloffset=+1]
 include::modules/rosa-policy-disaster-recovery.adoc[leveloffset=+1]

rosa_architecture/rosa_policy_service_definition/rosa-service-definition.adoc

@@ -33,11 +33,12 @@ include::modules/rosa-sdpolicy-instance-types.adoc[leveloffset=+2]
 
 For a detailed listing of supported instance types, see 
 ifdef::openshift-rosa-hcp[]
-xref:../rosa_policy_service_definition/rosa-hcp-instance-types.adoc#rosa-instance-types[{product-title} instance types].endif::openshift-rosa-hcp[]
+xref:../rosa_policy_service_definition/rosa-hcp-instance-types.adoc#rosa-instance-types[{product-title} instance types].
+endif::openshift-rosa-hcp[]
 ifndef::openshift-rosa-hcp[]
 xref:../rosa_policy_service_definition/rosa-instance-types.adoc#rosa-instance-types[{product-title} instance types].
 endif::openshift-rosa-hcp[]
-=======
+
 * xref:../rosa_policy_service_definition/rosa-instance-types.adoc#rosa-instance-types[{product-title} instance types]
 
 * xref:../../rosa_planning/rosa-limits-scalability.adoc#rosa-limits-scalability[Limits and scalability]