diff --git a/hosted_control_planes/index.adoc b/hosted_control_planes/index.adoc index 2f59e46bf78a..9f65d6b14ea8 100644 --- a/hosted_control_planes/index.adoc +++ b/hosted_control_planes/index.adoc @@ -1,15 +1,23 @@ :_mod-docs-content-type: ASSEMBLY -[id="hcp-overview"] include::_attributes/common-attributes.adoc[] +[id="hcp-overview"] = {hcp-capital} overview :context: hcp-overview -You can deploy {product-title} clusters by using two different control plane configurations: standalone or {hcp}. The standalone configuration uses dedicated virtual machines or physical machines to host the control plane. With {hcp} for {product-title}, you create control planes as pods on a management cluster without the need for dedicated virtual or physical machines for each control plane. +[role="_abstract"] +You can deploy {product-title} clusters by using two different control plane configurations: standalone or {hcp}. + +The standalone configuration uses dedicated virtual machines or physical machines to host the control plane. With {hcp} for {product-title}, you create control planes as pods on a management cluster without the need for dedicated virtual or physical machines for each control plane. toc::[] include::modules/hosted-control-planes-overview.adoc[leveloffset=+1] +[role="_additional-resources"] +.Additional resources + +* link:https://docs.redhat.com/en/documentation/red_hat_advanced_cluster_management_for_kubernetes/2.16/html/clusters/cluster_mce_overview#cluster_mce_overview[Cluster lifecycle with {mce} overview ({rh-rhacm-title} official documentation)] + include::modules/hcp-ocp-differences.adoc[leveloffset=+1] [role="_additional-resources"] @@ -20,6 +28,11 @@ include::modules/hcp-mce-acm-relationship-intro.adoc[leveloffset=+1] include::modules/hcp-acm-discover.adoc[leveloffset=+2] +[role="_additional-resources"] +.Additional resources + +* link:https://docs.redhat.com/en/documentation/red_hat_advanced_cluster_management_for_kubernetes/2.11/html/clusters/cluster_mce_overview#discover-hosted-acm[Discovering {mce-short} hosted clusters in {rh-rhacm-title} ({rh-rhacm-title} official documentation)] + include::modules/hosted-control-planes-version-support.adoc[leveloffset=+1] [role="_additional-resources"] diff --git a/modules/hcp-mce-acm-relationship-intro.adoc b/modules/hcp-mce-acm-relationship-intro.adoc index 03f2dd06adcb..8f67adcb57c5 100644 --- a/modules/hcp-mce-acm-relationship-intro.adoc +++ b/modules/hcp-mce-acm-relationship-intro.adoc @@ -6,11 +6,12 @@ [id="hcp-mce-acm-relationship-intro_{context}"] = Relationship between {hcp}, {mce-short}, and {rh-rhacm} -You can configure {hcp} by using the {mce}. The {mce-short} cluster lifecycle defines the process of creating, importing, managing, and destroying Kubernetes clusters across various infrastructure cloud providers, private clouds, and on-premises data centers. +[role="_abstract"] +You can configure {hcp} by using the {mce}. The {mce-short} cluster lifecycle defines the process of creating, importing, managing, and destroying Kubernetes clusters across various infrastructure cloud providers, private clouds, and on-premise data centers. [NOTE] ==== -The {mce-short} is an integral part of {rh-rhacm-first} and is enabled by default with {rh-rhacm}. However, you do not need {rh-rhacm} in order to use {hcp}. +The {mce-short} is an integral part of {rh-rhacm-title} and is enabled by default with {rh-rhacm}. However, you do not need {rh-rhacm-title} to use {hcp}. ==== The {mce-short} is the cluster lifecycle Operator that provides cluster management capabilities for {product-title} and {rh-rhacm} hub clusters. The {mce-short} enhances cluster fleet management and supports {product-title} cluster lifecycle management across clouds and data centers. diff --git a/modules/hcp-ocp-differences.adoc b/modules/hcp-ocp-differences.adoc index 177319058038..5fecc62dd2b6 100644 --- a/modules/hcp-ocp-differences.adoc +++ b/modules/hcp-ocp-differences.adoc @@ -6,8 +6,10 @@ [id="hcp-ocp-differences_{context}"] = Differences between {hcp} and {product-title} -{hcp-capital} is a form factor of {product-title}. Hosted clusters and the stand-alone {product-title} clusters are configured and managed differently. See the following tables to understand the differences between {product-title} and {hcp}: +[role="_abstract"] +{hcp-capital} is a form factor of {product-title}. Hosted clusters and the standalone {product-title} clusters are configured and managed differently. +See the following tables to understand the differences between {product-title} and {hcp}: [id="cluster-creation_{context}"] == Cluster creation and lifecycle diff --git a/modules/hosted-control-planes-overview.adoc b/modules/hosted-control-planes-overview.adoc index dc4727f4c358..47886f66df61 100644 --- a/modules/hosted-control-planes-overview.adoc +++ b/modules/hosted-control-planes-overview.adoc @@ -8,7 +8,8 @@ [id="hosted-control-planes-overview_{context}"] = Introduction to {hcp} -{hcp-capital} is available by using a link:https://docs.redhat.com/en/documentation/red_hat_advanced_cluster_management_for_kubernetes/2.16/html/clusters/cluster_mce_overview#cluster_mce_overview[supported version of {mce}] on the following platforms: +[role="_abstract"] +{hcp-capital} is available by using a supported version of {mce} on the following platforms: * Bare metal by using the Agent provider * Non-bare-metal Agent machines, as a Technology Preview feature @@ -22,7 +23,7 @@ The {hcp} feature is enabled by default. [NOTE] ==== -The {mce-short} is an integral part of {rh-rhacm-first} and is enabled by default with {rh-rhacm}. However, you do not need {rh-rhacm} in order to use {hcp}. +The {mce-short} is an integral part of {rh-rhacm-first} and is enabled by default with {rh-rhacm}. However, you do not need {rh-rhacm} to use {hcp}. ==== [id="hosted-control-planes-architecture_{context}"]