Swope getting started 1

clusters/about/cluster_mce_overview.adoc

@@ -3,7 +3,7 @@
 
 The {mce-short} is the cluster lifecycle operator that provides cluster management capabilities for {ocp-short} and {acm-short} hub clusters. From the hub cluster, you can create and manage clusters, as well as destroy any clusters that you created. You can also hibernate, resume, and detach clusters. 
 
-The {mce-short} is the cluster lifecycle operator that provides cluster management capabilities for {ocp} and {acm-short} hub clusters. If you installed {acm-short}, you do not need to install {mce-short}, as it is automatically installed. See other important information about Cluster lifecycle with {mce-short}:
+The {mce-short} is the cluster lifecycle operator that provides cluster management capabilities for {ocp-short} and {acm-short} hub clusters. If you installed {acm-short}, you do not need to install {mce-short}, as it is automatically installed. See other important information about Cluster lifecycle with {mce-short}:
 
 - Your cluster is created by using the {ocp-short} cluster installer with the Hive resource. See more information about the process of installing {ocp-short} clusters at link:https://docs.redhat.com/en/documentation/openshift_container_platform/4.17/html/installation_overview/index[Installing and configuring {ocp-short} clusters] in the {ocp-short} documentation.   
 
@@ -13,16 +13,15 @@ The {mce-short} is the cluster lifecycle operator that provides cluster manageme
 
 - If you subscribe to {acm-short}, you also receive the operator with installation. You can create, manage, and monitor other Kubernetes clusters with the {acm-short} hub cluster. 
 
-- Release images are the version of {ocp-short} that you use when you create a cluster. For clusters that are created using {acm-short}, you can enable automatic upgrading of your release images. For more information about release images in {acm-short}, see _Release images_.
-
-- With hosted control planes for {ocp-short}, you can create control planes as pods on a hosting cluster without the need for dedicated physical machines for each control plane. See the link:https://docs.redhat.com/en/documentation/openshift_container_platform/4.17/html/hosted_control_planes/hosted-control-planes-overview[Hosted control planes overview] in the {ocp-short} documentation. 
+- Release image versions are the versions of {ocp-short} that you use when you create a cluster. For clusters that are created using {acm-short}, you can enable automatic upgrading of your release images. For more information about release images in {acm-short}, see _Release images_.
 
 * xref:../cluster_lifecycle/cluster_lifecycle_arch.adoc#cluster-lifecycle-arch[Cluster lifecycle architecture]
 * xref:../release_notes/mce_release_notes.adoc#mce-release-notes[Release notes for Cluster lifecycle with {mce-short}]
 * xref:../install_upgrade/install_intro.adoc#mce-install-intro[Installing and upgrading {mce-short}]
 * xref:./mce_console.adoc#mce-console-overview[Console overview]
 * xref:./rbac_mce.adoc#mce-rbac[{mce} Role-based access control] 
-* xref:./mce_networking.adoc#mce-network-configuration[Network configuration]
+* xref:./mce_networking.adoc#mce-network-configuration[Network configuration for {mce-short}]
+* xref:./mce_hcp_overview.adoc#hcp-overview[Hosted control planes overview]
 * xref:../credentials/credential_intro.adoc#credentials[Managing credentials]
 * xref:../cluster_lifecycle/cluster_lifecycle_intro.adoc#cluster-intro[Cluster lifecycle introduction]
 * xref:../cluster_lifecycle/release_image_intro.adoc#release-images-intro[Release images]

clusters/about/mce_hcp_overview.adoc

@@ -0,0 +1,54 @@
+[#mce-hcp-overview]
+= Learn about hosted control planes with {mce-short}
+
+Hosted control planes represent a deployment model for {ocp-short} clusters that provides significant infrastructure efficiency. Instead of requiring dedicated virtual or physical machines for each cluster control plane, hosted control planes run as pods in a single namespace on a centralized management cluster.
+
+Standalone:: {ocp-short} clusters that use dedicated virtual or physical machines for the control plane components. Each cluster requires individual infrastructure for etcd, API servers, controller managers, and schedulers.
+
+Hosted:: A more efficient model where control planes run as pods on a shared management cluster. The hosted model offers the following advantages:
+
+- Reduces infrastructure overhead and costs
+- Enables faster cluster provisioning
+- Simplifies control plane management and updates
+- Allows for better resource utilization
+
+Get started with {hcp} clusters and {mce-short} by following the documentation and guidance. 
+
+* See the official {ocp-short} documentation in the link:https://docs.redhat.com/en/documentation/openshift_container_platform/4.18/html/hosted_control_planes/hosted-control-planes-overview[Hosted control planes overview] to learn more about hosted control planes.
+
+* Prepare your environment for hosted control planes. See the following documentation:
+
+    ** Find the requirements for your environment in link:https://docs.redhat.com/en/documentation/openshift_container_platform/4.18/html/hosted_control_planes/preparing-to-deploy-hosted-control-planes[Requirements for hosted control planes].
+
+    ** Get sizing guidance from link:https://docs.redhat.com/en/documentation/openshift_container_platform/4.18/html/hosted_control_planes/preparing-to-deploy-hosted-control-planes#sizing-guidance-for-hosted-control-planes[Sizing guidance for hosted control planes].
+
+* Learn to create hosted clusters. See link:https://docs.redhat.com/en/documentation/openshift_container_platform/4.18/html/hosted_control_planes/deploying-hosted-control-planes[Deploying hosted control planes]. You can create hosted clusters for the following platforms:
+
+    ** link:https://docs.redhat.com/en/documentation/openshift_container_platform/4.18/html/hosted_control_planes/deploying-hosted-control-planes#deploying-hosted-control-planes-on-aws[Deploying hosted control planes on AWS]
+    ** link:https://docs.redhat.com/en/documentation/openshift_container_platform/4.18/html/hosted_control_planes/deploying-hosted-control-planes#deploying-hosted-control-planes-on-bare-metal[Deploying hosted control planes on bare metal]
+    ** link:https://docs.redhat.com/en/documentation/openshift_container_platform/4.18/html/hosted_control_planes/deploying-hosted-control-planes#deploying-hosted-control-planes-on-openshift-virtualization[Deploying hosted control planes on OpenShift Virtualization]
+
+* You can manage hosted clusters with {mce-short}. See the following documentation:
+
+    ** *Optional:* Manually import a hosted cluster. See link:https://docs.redhat.com/en/documentation/openshift_container_platform/4.18/html/hosted_control_planes/manually-importing-a-hosted-cluster[Manually importing a hosted cluster].
+
+    ** Manage hosted clusters. See link:https://docs.redhat.com/en/documentation/openshift_container_platform/4.18/html/hosted_control_planes/managing-hosted-control-planes[Managing hosted control planes]. 
+
+    ** Learn about hosted control plane authentication, see https://docs.redhat.com/en/documentation/openshift_container_platform/4.17/html/hosted_control_planes/authentication-and-authorization-for-hosted-control-planes[Authentication and authorization for hosted control planes].
+
+    ** Learn about updating hosted clusters from the link:https://docs.redhat.com/en/documentation/openshift_container_platform/4.18/html/hosted_control_planes/updating-hosted-control-planes[Updating hosted control planes] documentation.
+
+    ** See link:https://docs.redhat.com/en/documentation/openshift_container_platform/4.18/html/hosted_control_planes/destroying-a-hosted-cluster[Destroying a hosted cluster] when you are ready.
+
+* With {acm-short} enabled, you can discover and manage hosted control plane clusters, while using {acm-short} capability. Learn about hosted control planes with {acm-short} from the following resources, which require {acm-short}:
+
+    ** Discover hosted control plane clusters. See link:https://docs.redhat.com/en/documentation/red_hat_advanced_cluster_management_for_kubernetes/2.13/html/multicluster_engine_operator_with_red_hat_advanced_cluster_management/mce-acm-integration#discover-hosted-acm[Discovering hosted control plane clusters with {acm-short}].
+
+    ** Set up disaster recovery for hosted control plane clusters with {acm-short}. See link:https://docs.redhat.com/en/documentation/red_hat_advanced_cluster_management_for_kubernetes/2.14/html/business_continuity/business-cont-overview#config-hcp-backup[Backup and restore for hosted control planes and hosted clusters].
+
+== Additional resources
+
+* See the release notes for hosted control planes at link:https://docs.redhat.com/en/documentation/openshift_container_platform/4.18/html/hosted_control_planes/hosted-control-planes-release-notes-1[Hosted control planes release notes].
+
+* See the Troubleshooting guide at link:https://docs.redhat.com/en/documentation/openshift_container_platform/4.18/html/hosted_control_planes/troubleshooting-hosted-control-planes[Troubleshooting hosted control planes].
+

clusters/about/mce_networking.adoc

@@ -1,5 +1,7 @@
 [#mce-network-configuration]
-= Network configuration
+= Network configuration for {mce-short}
+
+When you are installing bare metal managed clusters with the Infrastructure Operator, you must configure your network to allow certain connections between the hub cluster and the managed clusters.
 
 Configure your network settings to allow the connections.
 

clusters/install_upgrade/install_intro.adoc

@@ -17,7 +17,7 @@ See the following documentation:
 * xref:./config_infra_nodes_mce.adoc#config-infra-node-mce[Configuring infrastructure nodes for {mce-short}]
 * xref:./install_disconnected.adoc#install-on-disconnected-networks[Installing on disconnected networks]
 * xref:./uninstall.adoc#uninstalling-mce[Uninstalling]
-* xref:../about/mce_networking.adoc#mce-network-configuration[Network configuration]
+* xref:../about/mce_networking.adoc#mce-network-configuration[Network configuration for {mce-short}]
 * xref:../upgrade_cluster_disconnected_policies.adoc#upgrade-disconnect-cluster-policy[Upgrading disconnected clusters using policies]
 * xref:./adv_config_install.adoc#advanced-config-engine[MultiClusterEngine advanced configuration]
 * link:../../mce_acm_integration/mce_acm_intro.adoc#mce-acm-integration[{mce-short} with {acm-short} integration]

clusters/main.adoc

@@ -6,6 +6,7 @@ include::about/cluster_mce_overview.adoc[leveloffset=+1]
 include::about/mce_console.adoc[leveloffset=+2]
 include::about/rbac_mce.adoc[leveloffset=+2]
 include::about/mce_networking.adoc[leveloffset=+2]
+include::about/mce_hcp_overview.adoc[leveloffset=+2]
 include::release_notes/mce_release_notes.adoc[leveloffset=+2]
 include::release_notes/mce_new.adoc[leveloffset=+3]
 include::release_notes/mce_fixed_issues.adoc[leveloffset=+3]

networking/network_advanced.adoc

@@ -10,7 +10,7 @@
 [#network-configuration-additional]
 == Additional networking requirements for infrastructure operator table
 
-When you are installing bare metal managed clusters with the Infrastructure Operator, see link:../clusters/about/mce_networking.adoc#mce-network-configuration[Network configuration] in the {mce} documentation for additional networking requirements.
+When you are installing bare metal managed clusters with the Infrastructure Operator, see link:../clusters/about/mce_networking.adoc#mce-network-configuration[Network configuration for {mce-short}] in the {mce} documentation for additional networking requirements.
 
 [#network-configuration-submariner]
 == Submariner networking requirements table