[OSDOCS-15316]: Creating a hosted cluster on bare metal

Author: lahinson

hosted_control_planes/hcp-deploy/hcp-deploy-bm.adoc

@@ -65,12 +65,18 @@ include::modules/hcp-bm-create-infra-console.adoc[leveloffset=+2]
 
 * xref:../../web_console/web-console.adoc#web-console-overview[Accessing the web console]
 
-include::modules/hcp-bm-hc.adoc[leveloffset=+1]
+[id="hcp-bm-create-hc_{context}"]
+== Creating a hosted cluster on bare metal
+
+You can create a hosted cluster or import one. When the Assisted Installer is enabled as an add-on to {mce-short} and you create a hosted cluster with the Agent platform, the HyperShift Operator installs the Agent Cluster API provider in the hosted control plane namespace. 
+
+include::modules/hcp-bm-hc.adoc[leveloffset=+2]
 
 [role="_additional-resources"]
 .Additional resources
 
 * xref:../../hosted_control_planes/hcp-import.adoc[Manually importing a hosted cluster]
+* xref:../../hosted_control_planes/hcp-disconnected/hcp-dc-extract.adoc#hcp-dc-extract_hcp-deploy-dc-bm[Extracting the release image digest]
 
 include::modules/hcp-bm-hc-console.adoc[leveloffset=+2]
 

hosted_control_planes/hcp-deploy/hcp-deploy-ibm-power.adoc

@@ -36,7 +36,17 @@ include::modules/hcp-ibm-power-infra-reqs.adoc[leveloffset=+1]
 
 include::modules/hcp-ibm-power-dns.adoc[leveloffset=+1]
 
-include::modules/hcp-bm-hc.adoc[leveloffset=+1]
+[id="hcp-bm-create-hc-ibm-power"]
+== Creating a hosted cluster on bare metal
+
+You can create a hosted cluster or import one. When the Assisted Installer is enabled as an add-on to {mce-short} and you create a hosted cluster with the Agent platform, the HyperShift Operator installs the Agent Cluster API provider in the hosted control plane namespace.
+
+include::modules/hcp-bm-hc.adoc[leveloffset=+2]
+
+[role="_additional-resources"]
+.Additional resources
+* xref:../../hosted_control_planes/hcp-import.adoc[Manually importing a hosted cluster]
+* xref:../../hosted_control_planes/hcp-disconnected/hcp-dc-extract.adoc#hcp-dc-extract_hcp-deploy-dc-bm[Extracting the release image digest]
 
 [id="hcp-ibm-power-heterogeneous-nodepools_{context}"]
 == Creating heterogeneous node pools on agent hosted clusters

hosted_control_planes/hcp-deploy/hcp-deploy-ibmz.adoc

@@ -41,11 +41,18 @@ include::modules/hcp-ibm-z-infra-reqs.adoc[leveloffset=+1]
 * xref:../../hosted_control_planes/hcp-prepare/hcp-enable-disable.adoc[Enabling or disabling the {hcp} feature]
 
 include::modules/hcp-ibm-z-dns.adoc[leveloffset=+1]
-include::modules/hcp-bm-hc.adoc[leveloffset=+1]
+
+[id="hcp-bm-create-hc-ibm-z"]
+== Creating a hosted cluster on bare metal
+
+You can create a hosted cluster or import one. When the Assisted Installer is enabled as an add-on to {mce-short} and you create a hosted cluster with the Agent platform, the HyperShift Operator installs the Agent Cluster API provider in the hosted control plane namespace. 
+
+include::modules/hcp-bm-hc.adoc[leveloffset=+2]
 
 [role="_additional-resources"]
 .Additional resources
-
+* xref:../../hosted_control_planes/hcp-import.adoc[Manually importing a hosted cluster]
+* xref:../../hosted_control_planes/hcp-disconnected/hcp-dc-extract.adoc#hcp-dc-extract_hcp-deploy-dc-bm[Extracting the release image digest]
 * xref:../../hosted_control_planes/hcp-deploy/hcp-deploy-bm.adoc#hcp-bm-hc-console_hcp-deploy-bm[Creating a hosted cluster on bare metal by using the console]
 
 include::modules/hcp-ibm-z-infraenv.adoc[leveloffset=+1]

modules/hcp-bm-autoscale.adoc

@@ -2,6 +2,7 @@
 //
 // * hosted_control_planes/hcp-manage/hcp-manage-bm.adoc
 // * hosted_control_planes/hcp-manage/hcp-manage-non-bm.adoc
+// * hosted_control_planes/hcp-manage/hcp-manage-virt.adoc
 
 :_mod-docs-content-type: PROCEDURE
 [id="hcp-bm-autoscale_{context}"]

modules/hcp-bm-dns.adoc

@@ -8,7 +8,7 @@
 
 The API Server for the hosted cluster is exposed as a `NodePort` service. A DNS entry must exist for `api.<hosted_cluster_name>.<base_domain>` that points to destination where the API Server can be reached.
 
-The DNS entry can be as simple as a record that points to one of the nodes in the managed cluster that is running the hosted control plane. The entry can also point to a load balancer that is deployed to redirect incoming traffic to the ingress pods. 
+The DNS entry can be as simple as a record that points to one of the nodes in the management cluster that is running the hosted control plane. The entry can also point to a load balancer that is deployed to redirect incoming traffic to the ingress pods. 
 
 .Example DNS configuration
 [source,terminal]
@@ -22,6 +22,11 @@ api-int.example.krnl.es.    IN A 192.168.122.22
 `*`.apps.example.krnl.es. IN A 192.168.122.23
 ----
 
+[NOTE]
+====
+In the previous example, `*.apps.example.krnl.es. IN A 192.168.122.23` is either a node in the hosted cluster or a load balancer, if one has been configured.
+====
+
 If you are configuring DNS for a disconnected environment on an IPv6 network, the configuration looks like the following example.
 
 .Example DNS configuration for an IPv6 network