Merge pull request #68683 from EricPonvelle/OSDOCS-6139-2_HCP-GA-Updates

OSDOCS-6139.2: Updating ROSA with HCP docs for GA

Author: wgordon17

_topic_maps/_topic_map_rosa.yml

@@ -65,6 +65,10 @@ Topics:
     File: rosa-service-definition
   - Name: ROSA update life cycle
     File: rosa-life-cycle
+  - Name: ROSA with HCP service definition
+    File: rosa-hcp-service-definition
+  - Name: ROSA with HCP update life cycle
+    File: rosa-hcp-life-cycle
   - Name: Understanding security for ROSA
     File: rosa-policy-process-security
   - Name: SRE and service account access
@@ -271,6 +275,8 @@ Topics:
 #    File: troubleshooting-installations
   - Name: Troubleshooting ROSA installations
     File: rosa-troubleshooting-installations
+  - Name: Troubleshooting networking
+    File: rosa-troubleshooting-networking
   - Name: Verifying node health
     File: verifying-node-health
 #  cannot create resource "namespaces", cannot patch resource "nodes"

modules/custom-tuning-specification.adoc

@@ -191,7 +191,7 @@ The list items `match` and `machineConfigLabels` are connected by the logical OR
 When using machine config pool based matching, it is advised to group nodes with the same hardware configuration into the same machine config pool. Not following this practice might result in TuneD operands calculating conflicting kernel parameters for two or more nodes sharing the same machine config pool.
 ====
 
-.Example: node or pod label based matching
+.Example: Node or pod label based matching
 
 ifndef::rosa-hcp-tuning[]
 [source,yaml]
@@ -263,7 +263,7 @@ Finally, the profile `openshift-node` has the lowest priority of `30`. It lacks
 
 image::node-tuning-operator-workflow-revised.png[Decision workflow]
 
-.Example: machine config pool based matching
+.Example: Machine config pool based matching
 ifndef::rosa-hcp-tuning[]
 [source,yaml]
 ----

modules/life-cycle-dates.adoc

@@ -1,20 +1,33 @@
 // Module included in the following assemblies:
 //
-// * osd_architecture/osd_policy/osd-life-cycle.adoc
 // * rosa_architecture/rosa_policy_service_definition/rosa-life-cycle.adoc
+// * rosa_architecture/rosa_policy_service_definition/rosa-hcp-life-cycle.adoc
+// * osd_architecture/osd_policy/osd-life-cycle.adoc
+
+ifeval::["{context}" == "rosa-hcp-life-cycle"]
+:rosa-with-hcp:
+endif::[]
 
 [id="sd-life-cycle-dates_{context}"]
 = Life cycle dates
 
 [options="header"]
 |===
 |Version    |General availability   |End of life
+ifdef::rosa-with-hcp[]
+|4.14       |Dec 4, 2023            |Feb 28, 2025
+endif::rosa-with-hcp[]
+ifndef::rosa-with-hcp[]
 |4.14       |Oct 31, 2023           |Feb 28, 2025
 |4.13       |May 17, 2023           |Sep 17, 2024
 |4.12       |Jan 17, 2023           |May 17, 2024
 |4.11       |Aug 10, 2022           |Dec 10, 2023
 |4.10       |Mar 10, 2022           |Sep 10, 2023
 |4.9        |Oct 18, 2021           |Dec 18, 2022
 |4.8        |Jul 27, 2021           |Sep 27, 2022
-
+endif::rosa-with-hcp[]
 |===
+
+ifeval::["{context}" == "rosa-hcp-life-cycle"]
+:!rosa-with-hcp:
+endif::[]

modules/life-cycle-limited-support.adoc

@@ -1,19 +1,30 @@
 // Module included in the following assemblies:
 //
 // * rosa_architecture/rosa_policy_service_definition/rosa-life-cycle.adoc
+// * rosa_architecture/rosa_policy_service_definition/rosa-hcp-life-cycle.adoc
 // * osd_architecture/osd_policy/osd-life-cycle.adoc
 
+ifeval::["{context}" == "rosa-hcp-life-cycle"]
+:rosa-with-hcp:
+endif::[]
+
 [id="rosa-limited-support_{context}"]
 = Limited support status
 
 When a cluster transitions to a _Limited Support_ status, Red Hat no longer proactively monitors the cluster, the SLA is no longer applicable, and credits requested against the SLA are denied. It does not mean that you no longer have product support. In some cases, the cluster can return to a fully-supported status if you remediate the violating factors. However, in other cases, you might have to delete and recreate the cluster.
 
 A cluster might transition to a Limited Support status for many reasons, including the following scenarios:
 
+ifndef::rosa-with-hcp[]
 If you do not upgrade a cluster to a supported version before the end-of-life date:: Red Hat does not make any runtime or SLA guarantees for versions after their end-of-life date. To receive continued support, upgrade the cluster to a supported version prior to the end-of-life date. If you do not upgrade the cluster prior to the end-of-life date, the cluster transitions to a Limited Support status until it is upgraded to a supported version.
 +
 Red Hat provides commercially reasonable support to upgrade from an unsupported version to a supported version. However, if a supported upgrade path is no longer available, you might have to create a new cluster and migrate your workloads.
+endif::rosa-with-hcp[]
 
 If you remove or replace any native {product-title} components or any other component that is installed and managed by Red Hat:: If cluster administrator permissions were used, Red Hat is not responsible for any of your or your authorized users’ actions, including those that affect infrastructure services, service availability, or data loss. If Red Hat detects any such actions, the cluster might transition to a Limited Support status. Red Hat notifies you of the status change and you should either revert the action or create a support case to explore remediation steps that might require you to delete and recreate the cluster.
 
 If you have questions about a specific action that might cause a cluster to transition to a Limited Support status or need further assistance, open a support ticket.
+
+ifeval::["{context}" == "rosa-hcp-life-cycle"]
+:!rosa-with-hcp:
+endif::[]

modules/life-cycle-mandatory-upgrades.adoc

@@ -1,15 +1,27 @@
 // Module included in the following assemblies:
 // * rosa_architecture/rosa_policy_service_definition/rosa-life-cycle.adoc
+// * rosa_architecture/rosa_policy_service_definition/rosa-hcp-life-cycle.adoc
 // * osd_architecture/osd_policy/osd-life-cycle.adoc
 
+ifeval::["{context}" == "rosa-hcp-life-cycle"]
+:rosa-with-hcp:
+endif::[]
+
 :_mod-docs-content-type: REFERENCE
 [id="rosa-mandatory-upgrades_{context}"]
 = Mandatory upgrades
 
-In the event that a Critical or Important CVE, or other bug identified by Red Hat, significantly
-impacts the security or stability of the cluster, the customer must upgrade to the next supported
-patch release within two link:https://access.redhat.com/articles/2623321[business days].
+If a critical or important CVE, or other bug identified by Red Hat, significantly impacts the security or stability of the cluster, the customer must upgrade to the next supported patch release within two link:https://access.redhat.com/articles/2623321[business days].
+
+In extreme circumstances and based on Red Hat's assessment of the CVE criticality to the environment, Red Hat will notify customers that they have two link:https://access.redhat.com/articles/2623321[business days] to schedule or manually update their cluster to the latest, secure patch release. In the case that an update is not performed after two link:https://access.redhat.com/articles/2623321[business days], Red Hat will automatically update the
+ifdef::rosa-with-hcp[]
+cluster's control plane
+endif::rosa-with-hcp[]
+ifndef::rosa-with-hcp[]
+cluster
+endif::rosa-with-hcp[]
+to the latest, secure patch release to mitigate potential security breach(es) or instability. Red Hat might, at its own discretion, temporarily delay an automated update if requested by a customer through a link:https://access.redhat.com/support[support case].
 
-In extreme circumstances and based on Red Hat's assessment of the CVE criticality to the
-environment, Red Hat will notify customers that they have two link:https://access.redhat.com/articles/2623321[business days] to schedule or manually update their cluster to the latest, secure patch release.
-In the case that an update is not performed after two link:https://access.redhat.com/articles/2623321[business days], Red Hat will automatically update the cluster to the latest, secure patch release to mitigate potential security breach(es) or instability. Red Hat may, at its own discretion, temporarily delay an automated update if requested by a customer through a link:https://access.redhat.com/support[support case].
+ifeval::["{context}" == "rosa-hcp-life-cycle"]
+:!rosa-with-hcp:
+endif::[]

modules/life-cycle-minor-versions.adoc

@@ -1,22 +1,36 @@
 // Module included in the following assemblies:
 // * rosa_architecture/rosa_policy_service_definition/rosa-life-cycle.adoc
+// * rosa_architecture/rosa_policy_service_definition/rosa-hcp-life-cycle.adoc
 // * osd_architecture/osd_policy/osd-life-cycle.adoc
 
+ifeval::["{context}" == "rosa-hcp-life-cycle"]
+:rosa-with-hcp:
+endif::[]
+
 [id="rosa-minor-versions_{context}"]
 = Minor versions (x.Y.z)
 
-Starting with the 4.8 OpenShift Container Platform minor version, Red Hat supports all minor
-versions for at least a 16 month period following general availability of the given minor version. Patch
-versions are not affected by the support period.
+Starting with the 4.8 OpenShift Container Platform minor version, Red Hat supports all minor versions for at least a 16 month period following general availability of the given minor version. Patch versions are not affected by the support period.
 
-Customers are notified 60, 30, and 15 days prior to the end of the support period. Clusters must be upgraded to
-a supported minor version prior to the end of the support period, or the cluster will enter
-a "Limited Support" status.
+Customers are notified 60, 30, and 15 days before the end of the support period. Clusters must be upgraded to the latest patch version of the oldest supported minor version before the end of the support period, or
+ifdef::rosa-with-hcp[]
+Red Hat will automatically upgrade the control plane to the next supported minor version.
+endif::rosa-with-hcp[]
+ifndef::rosa-with-hcp[]
+the cluster will enter a "Limited Support" status.
+endif::rosa-with-hcp[]
 
 .Example
-. A customer's cluster is currently running on 4.13.8. The 4.13 minor version became generally
-  available on May 17, 2023.
-. On July 19, August 16, and September 2, 2024, the customer is notified that their cluster will enter "Limited Support" status
-  on September 17, 2024 if the cluster has not already been upgraded to a supported minor version.
+. A customer's cluster is currently running on 4.13.8. The 4.13 minor version became generally available on May 17, 2023.
+. On July 19, August 16, and September 2, 2024, the customer is notified that their cluster will enter "Limited Support" status on September 17, 2024 if the cluster has not already been upgraded to a supported minor version.
 . The cluster must be upgraded to 4.14 or later by September 17, 2024.
-. If the upgrade has not been performed, the cluster will be flagged as being in a "Limited Support" status.
+ifdef::rosa-with-hcp[]
+. If the upgrade has not been performed, the cluster's control plane will be automatically upgraded to 4.14.26, and there will be no automatic upgrades to the cluster's worker nodes.
+endif::rosa-with-hcp[]
+ifndef::rosa-with-hcp[]
+. If the upgrade has not been performed, the cluster will be flagged as being in a "Limited Support" status.
+endif::rosa-with-hcp[]
+
+ifeval::["{context}" == "rosa-hcp-life-cycle"]
+:!rosa-with-hcp:
+endif::[]

modules/rosa-sdpolicy-am-compute.adoc

@@ -2,17 +2,28 @@
 // Module included in the following assemblies:
 //
 // * rosa_architecture/rosa_policy_service_definition/rosa-service-definition.adoc
+// * rosa_architecture/rosa_policy_service_definition/rosa-hcp-service-definition.adoc
+
+ifeval::["{context}" == "rosa-hcp-service-definition"]
+:rosa-with-hcp:
+endif::[]
+
 :_mod-docs-content-type: CONCEPT
 [id="rosa-sdpolicy-instance-types_{context}"]
 = Instance types
 
+ifdef::rosa-with-hcp[]
+All {hcp-title} clusters require a minimum of 2 worker nodes. All {hcp-title} clusters support a maximum of 51 worker nodes. Shutting down the underlying infrastructure through the cloud provider console is unsupported and can lead to data loss.
+endif::rosa-with-hcp[]
+ifndef::rosa-with-hcp[]
 Single availability zone clusters require a minimum of 3 control plane nodes, 2 infrastructure nodes, and 2 worker nodes deployed to a single availability zone.
 
 Multiple availability zone clusters require a minimum of 3 control plane nodes, 3 infrastructure nodes, and 3 worker nodes. Additional nodes must be purchased in multiples of three to maintain proper node distribution.
 
 All {product-title} clusters support a maximum of 180 worker nodes.
 
 Control plane and infrastructure nodes are deployed and managed by Red Hat. Shutting down the underlying infrastructure through the cloud provider console is unsupported and can lead to data loss. There are at least 3 control plane nodes that handle etcd- and API-related workloads. There are at least 2 infrastructure nodes that handle metrics, routing, the web console, and other workloads. You must not run any workloads on the control and infrastructure nodes. Any workloads you intend to run must be deployed on worker nodes. See the Red Hat Operator support section below for more information about Red Hat workloads that must be deployed on worker nodes.
+endif::rosa-with-hcp[]
 
 [NOTE]
 ====
@@ -22,3 +33,7 @@ Approximately one vCPU core and 1 GiB of memory are reserved on each worker node
 
 For additional information, see the link:https://kubernetes.io/docs/tasks/administer-cluster/reserve-compute-resources/#system-reserved[Kubernetes documentation].
 ====
+
+ifeval::["{context}" == "rosa-hcp-service-definition"]
+:!rosa-with-hcp:
+endif::[]

modules/rosa-sdpolicy-am-limited-support.adoc

@@ -2,6 +2,12 @@
 // Module included in the following assemblies:
 //
 // * rosa_architecture/rosa_policy_service_definition/rosa-service-definition.adoc
+// * rosa_architecture/rosa_policy_service_definition/rosa-hcp-service-definition.adoc
+
+ifeval::["{context}" == "rosa-hcp-service-definition"]
+:rosa-with-hcp:
+endif::[]
+
 :_mod-docs-content-type: CONCEPT
 [id="rosa-limited-support_{context}"]
 = Limited support status
@@ -10,10 +16,15 @@ When a cluster transitions to a _Limited Support_ status, Red Hat no longer proa
 
 A cluster might move to a Limited Support status for many reasons, including the following scenarios:
 
+ifndef::rosa-with-hcp[]
 If you do not upgrade a cluster to a supported version before the end-of-life date:: Red Hat does not make any runtime or SLA guarantees for versions after their end-of-life date. To receive continued support, upgrade the cluster to a supported version prior to the end-of-life date. If you do not upgrade the cluster prior to the end-of-life date, the cluster transitions to a Limited Support status until it is upgraded to a supported version.
 +
 Red Hat provides commercially reasonable support to upgrade from an unsupported version to a supported version. However, if a supported upgrade path is no longer available, you might have to create a new cluster and migrate your workloads.
 
+endif::rosa-with-hcp[]
 If you remove or replace any native {product-title} components or any other component that is installed and managed by Red Hat:: If cluster administrator permissions were used, Red Hat is not responsible for any of your or your authorized users’ actions, including those that affect infrastructure services, service availability, or data loss. If Red Hat detects any such actions, the cluster might transition to a Limited Support status. Red Hat notifies you of the status change and you should either revert the action or create a support case to explore remediation steps that might require you to delete and recreate the cluster.
 
-If you have questions about a specific action that might cause a cluster to move to a Limited Support status or need further assistance, open a support ticket.
+If you have questions about a specific action that might cause a cluster to move to a Limited Support status or need further assistance, open a support ticket.
+ifeval::["{context}" == "rosa-hcp-service-definition"]
+:!rosa-with-hcp:
+endif::[]

modules/rosa-sdpolicy-am-local-zones.adoc

@@ -1,11 +1,27 @@
 
 // Module included in the following assemblies:
 //
-// * assemblies/rosa-service-definition.adoc
+// * rosa_architecture/rosa_policy_service_definition/rosa-service-definition.adoc
+// * rosa_architecture/rosa_policy_service_definition/rosa-hcp-service-definition.adoc
+
 :_mod-docs-content-type: CONCEPT
+
+ifeval::["{context}" == "rosa-hcp-service-definition"]
+:rosa-with-hcp:
+endif::[]
+
 [id="rosa-sdpolicy-am-local-zones_{context}"]
 = Local Zones
 
+ifdef::rosa-with-hcp[]
+{hcp-title-first} does not support the use of AWS Local Zones.
+endif::rosa-with-hcp[]
+ifndef::rosa-with-hcp[]
 {product-title} supports the use of AWS Local Zones, which are metropolis-centralized availability zones where customers can place latency-sensitive application workloads. Local Zones are extensions of AWS Regions that have their own internet connection. For more information about AWS Local Zones, see the AWS documentation link:https://docs.aws.amazon.com/local-zones/latest/ug/how-local-zones-work.html[How Local Zones work].
 
-For steps to enable AWS Local Zones and add a Local Zone to a machine pool, see xref:../../rosa_cluster_admin/rosa_nodes/rosa-nodes-machinepools-configuring.adoc#rosa-nodes-machine-pools-local-zones[Configuring Local Zones for machine pulls].
+For steps to enable AWS Local Zones and add a Local Zone to a machine pool, see xref:../../rosa_cluster_admin/rosa_nodes/rosa-nodes-machinepools-configuring.adoc#rosa-nodes-machine-pools-local-zones[Configuring Local Zones for machine pulls].
+endif::rosa-with-hcp[]
+
+ifeval::["{context}" == "rosa-hcp-service-definition"]
+:!rosa-with-hcp:
+endif::[]