Merge pull request #80323 from lahinson/osdocs-10966-move-hcp

lahinson · web-flow · commit 43a874162740 · 2024-08-13T11:52:14.000-04:00
[OSDOCS-10966]: Reorganizing and updating HCP overview
diff --git a/architecture/control-plane.adoc b/architecture/control-plane.adoc
@@ -33,6 +33,13 @@ endif::openshift-dedicated,openshift-rosa[]
 
 include::modules/architecture-machine-roles.adoc[leveloffset=+1]
 
+// This additional resource does not apply to OSD/ROSA
+ifndef::openshift-dedicated,openshift-rosa[]
+[role="_additional-resources"]
+.Additional resources
+* xref:../hosted_control_planes/index.adoc#hcp-overview[{hcp-capital} overview]
+endif::openshift-dedicated,openshift-rosa[]
+
 include::modules/operators-overview.adoc[leveloffset=+1]
 
 ifdef::openshift-enterprise,openshift-webscale,openshift-origin[]
@@ -80,15 +87,4 @@ ifndef::openshift-dedicated,openshift-rosa[]
 .Additional resources
 * xref:../scalability_and_performance/recommended-performance-scale-practices/recommended-etcd-practices.adoc#recommended-etcd-practices[Recommended etcd practices]
 * xref:../backup_and_restore/control_plane_backup_and_restore/backing-up-etcd.adoc#backing-up-etcd[Backing up etcd]
-endif::openshift-dedicated,openshift-rosa[]
-
-ifndef::openshift-dedicated,openshift-rosa[]
-include::modules/hosted-control-planes-overview.adoc[leveloffset=+1]
-
-[role="_additional-resources"]
-.Additional resources
-* link:https://access.redhat.com/documentation/en-us/red_hat_advanced_cluster_management_for_kubernetes/2.9/html/clusters/cluster_mce_overview#hosted-control-planes-intro[{hcp-capital}]
-
-include::modules/hosted-control-planes-concepts-personas.adoc[leveloffset=+2]
-include::modules/hosted-control-planes-version-support.adoc[leveloffset=+2]
-endif::openshift-dedicated,openshift-rosa[]
+endif::openshift-dedicated,openshift-rosa[]
diff --git a/architecture/index.adoc b/architecture/index.adoc
@@ -61,6 +61,13 @@ Operators are important components in {product-title} because they provide the f
 * Manage over-the-air updates
 * Ensure applications stay in the specified state
 
+ifndef::openshift-dedicated,openshift-rosa[]
+[role="_additional-resources"]
+.Additional resources
+
+* xref:../hosted_control_planes/index.adoc#hcp-overview[{hcp-capital} overview]
+endif::openshift-dedicated,openshift-rosa[]
+
 [id="about-containerized-applications-for-developers"]
 == About containerized applications for developers
 
diff --git a/architecture/mce-overview-ocp.adoc b/architecture/mce-overview-ocp.adoc
@@ -16,7 +16,7 @@ One of the challenges of scaling Kubernetes environments is managing the lifecyc
 
 When you enable multicluster engine on {product-title}, you gain the following capabilities:
 
-* xref:../architecture/control-plane.adoc#hosted-control-planes-overview_control-plane[{hcp-capital}], which is a feature that is based on the HyperShift project. With a centralized hosted control plane, you can operate {product-title} clusters in a hyperscale manner.
+* xref:../hosted_control_planes/index.adoc#hcp-overview[{hcp-capital}], which is a feature that is based on the HyperShift project. With a centralized hosted control plane, you can operate {product-title} clusters in a hyperscale manner.
 * Hive, which provisions self-managed {product-title} clusters to the hub and completes the initial configurations for those clusters.
 * klusterlet agent, which registers managed clusters to the hub.
 * Infrastructure Operator, which manages the deployment of the Assisted Service to orchestrate on-premise bare metal and vSphere installations of {product-title}, such as {sno} on bare metal. The Infrastructure Operator includes xref:../edge_computing/ztp-deploying-far-edge-clusters-at-scale.adoc#ztp-challenges-of-far-edge-deployments_ztp-deploying-far-edge-clusters-at-scale[{ztp-first}], which fully automates cluster creation on bare metal and vSphere provisioning with GitOps workflows to manage deployments and configuration changes.
diff --git a/hosted_control_planes/index.adoc b/hosted_control_planes/index.adoc
@@ -8,18 +8,13 @@ You can deploy {product-title} clusters by using two different control plane con
 
 toc::[]
 
-include::modules/hosted-control-planes-concepts-personas.adoc[leveloffset=+1]
 include::modules/hosted-control-planes-overview.adoc[leveloffset=+1]
-
-[role="_additional-resources"]
-.Additional resources
-
-* link:https://access.redhat.com/documentation/en-us/red_hat_advanced_cluster_management_for_kubernetes/2.9/html/clusters/cluster_mce_overview#hosted-control-planes-intro[{hcp-capital}]
-
 include::modules/hosted-control-planes-version-support.adoc[leveloffset=+1]
 
 [role="_additional-resources"]
 .Additional resources
 
 * xref:../scalability_and_performance/using-node-tuning-operator.adoc#node-tuning-hosted-cluster_node-tuning-operator[Configuring node tuning in a hosted cluster]
 * xref:../scalability_and_performance/using-node-tuning-operator.adoc#advanced-node-tuning-hosted-cluster_node-tuning-operator[Advanced node tuning for hosted clusters by setting kernel boot parameters]
+
+include::modules/hosted-control-planes-concepts-personas.adoc[leveloffset=+1]
diff --git a/modules/hosted-control-planes-overview.adoc b/modules/hosted-control-planes-overview.adoc
@@ -8,16 +8,17 @@
 [id="hosted-control-planes-overview_{context}"]
 = Introduction to {hcp}
 
-You can use {hcp} for Red Hat {product-title} to reduce management costs, optimize cluster deployment time, and separate management and workload concerns so that you can focus on your applications.
-
-{hcp-capital} is available by using the link:https://access.redhat.com/documentation/en-us/red_hat_advanced_cluster_management_for_kubernetes/2.9/html/clusters/cluster_mce_overview#cluster_mce_overview[{mce} version 2.0 or later] on the following platforms:
+{hcp-capital} is available by using the link:https://access.redhat.com/documentation/en-us/red_hat_advanced_cluster_management_for_kubernetes/2.11/html/clusters/cluster_mce_overview#cluster_mce_overview[{mce} version 2.0 or later] on the following platforms:
 
 * Bare metal by using the Agent provider
+* Non-bare metal Agent machines
 * {VirtProductName}, as a Generally Available feature in connected environments and a Technology Preview feature in disconnected environments
-* {aws-first}, as a Technology Preview feature
+* {aws-first}
 * {ibm-z-title}, as a Technology Preview feature
 * {ibm-power-title}, as a Technology Preview feature
 
+The {hcp} feature is enabled by default.
+
 [id="hosted-control-planes-architecture_{context}"]
 == Architecture of {hcp}
 
@@ -32,7 +33,7 @@ image::hosted-control-planes-diagram.png[Diagram that compares the hosted contro
 [id="hosted-control-planes-benefits_{context}"]
 == Benefits of {hcp}
 
-With {hcp} for {product-title}, you can pave the way for a true hybrid-cloud approach and enjoy several other benefits.
+With {hcp}, you can pave the way for a true hybrid-cloud approach and enjoy several other benefits.
 
 * The security boundaries between management and workloads are stronger because the control plane is decoupled and hosted on a dedicated hosting service cluster. As a result, you are less likely to leak credentials for clusters to other users. Because infrastructure secret account management is also decoupled, cluster infrastructure administrators cannot accidentally delete control plane infrastructure.
 
