Merge pull request #80675 from lahinson/osdocs-11001-hcp-disconnected

[OSDOCS-11001]: Moving HCP disconnected docs

Author: lahinson

_topic_maps/_topic_map.yml

@@ -2425,7 +2425,7 @@ Topics:
     File: hcp-deploy-aws
   - Name: Deploying hosted control planes on bare metal
     File: hcp-deploy-bm
-  - Name: Deploying hosted conrol planes on OpenShift Virtualization
+  - Name: Deploying hosted control planes on OpenShift Virtualization
     File: hcp-deploy-virt
   - Name: Deploying hosted control planes on non-bare metal agent machines
     File: hcp-deploy-non-bm
@@ -2446,10 +2446,17 @@ Topics:
     File: hcp-manage-non-bm
   - Name: Managing hosted control planes on IBM Power
     File: hcp-manage-ibmpower
-- Name: Preparing to deploy hosted control planes in a disconnected environment
-  File: hcp-prepare-disconnected
 - Name: Deploying hosted control planes in a disconnected environment
-  File: hcp-deploy-disconnected
+  Dir: hcp-disconnected
+  Topics:
+  - Name: Introduction to hosted control planes in a disconnected environment
+    File: hcp-deploy-dc
+  - Name: Deploying hosted control planes on OpenShift Virtualization in a disconnected environment
+    File: hcp-deploy-dc-virt
+  - Name: Deploying hosted control planes on bare metal in a disconnected environment
+    File: hcp-deploy-dc-bm
+  - Name: Monitoring user workload in a disconnected environment
+    File: hcp-dc-monitor
 - Name: Updating hosted control planes
   File: hcp-updating
 - Name: High availability for hosted control planes

hosted_control_planes/hcp-deploy-disconnected.adoc

@@ -0,0 +1 @@
+../../_attributes/

hosted_control_planes/hcp-disconnected/_attributes

@@ -0,0 +1,13 @@
+:_mod-docs-content-type: ASSEMBLY
+[id="hcp-dc-monitor"]
+include::_attributes/common-attributes.adoc[]
+= Monitoring user workload in a disconnected environment
+:context: hcp-dc-monitor
+
+toc::[]
+
+The `hypershift-addon` managed cluster add-on enables the `--enable-uwm-telemetry-remote-write` option in the HyperShift Operator. By enabling that option, you ensure that user workload monitoring is enabled and that it can remotely write telemetry metrics from control planes. 
+
+include::modules/hcp-dc-usr-wkld.adoc[leveloffset=+1]
+include::modules/hcp-dc-verify.adoc[leveloffset=+1]
+include::modules/hcp-dc-addon.adoc[leveloffset=+1]

hosted_control_planes/hcp-disconnected/hcp-dc-monitor.adoc

@@ -0,0 +1,54 @@
+:_mod-docs-content-type: ASSEMBLY
+[id="hcp-deploy-dc-bm"]
+include::_attributes/common-attributes.adoc[]
+= Deploying {hcp} on bare metal in a disconnected environment
+:context: hcp-deploy-dc-bm
+
+toc::[]
+
+When you provision hosted control planes on bare metal, you use the Agent platform. The Agent platform and {mce} work together to enable disconnected deployments. The Agent platform uses the central infrastructure management service to add worker nodes to a hosted cluster. For an introduction to the central infrastructure management service, see link:https://docs.redhat.com/en/documentation/red_hat_advanced_cluster_management_for_kubernetes/2.11/html/clusters/cluster_mce_overview#enable-cim[Enabling the central infrastructure management service].
+
+include::modules/hcp-dc-bm-arch.adoc[leveloffset=+1]
+include::modules/hcp-dc-bm-reqs.adoc[leveloffset=+1]
+include::modules/hcp-dc-extract.adoc[leveloffset=+1]
+include::modules/hcp-dc-hypervisor.adoc[leveloffset=+1]
+include::modules/hcp-bm-dns.adoc[leveloffset=+1]
+include::modules/hcp-dc-registry.adoc[leveloffset=+1]
+include::modules/hcp-dc-mgmt-cluster.adoc[leveloffset=+1]
+include::modules/hcp-dc-web-server.adoc[leveloffset=+1]
+include::modules/hcp-dc-image-mirror.adoc[leveloffset=+1]
+include::modules/hcp-dc-apply-objects.adoc[leveloffset=+1]
+
+[role="_additional-resources"]
+.Additional resources
+* xref:../../disconnected/mirroring/installing-mirroring-disconnected.adoc#installing-mirroring-disconnected[Mirroring images for a disconnected installation using the oc-mirror plugin].
+
+[id="hcp-dc-mce-bm"]
+== Deploying {mce-short} for a disconnected installation of {hcp}
+
+The {mce} plays a crucial role in deploying clusters across providers. If you do not have {mce-short} installed, review the following documentation to understand the prerequisites and steps to install it:
+
+* link:https://docs.redhat.com/en/documentation/red_hat_advanced_cluster_management_for_kubernetes/2.11/html/clusters/cluster_mce_overview#mce-intro[About cluster lifecycle with multicluster engine operator]
+* link:https://docs.redhat.com/en/documentation/red_hat_advanced_cluster_management_for_kubernetes/2.11/html/clusters/cluster_mce_overview#mce-install-intro[Installing and upgrading multicluster engine operator]
+
+include::modules/hcp-agentserviceconfig.adoc[leveloffset=+2]
+
+[id="hcp-dc-tls-bm"]
+== Configuring TLS certificates for a disconnected installation of {hcp}
+
+To ensure proper function in a disconnected deployment, you need to configure the registry CA certificates in the management cluster and the worker nodes for the hosted cluster.
+
+include::modules/hcp-dc-tls-mgmt.adoc[leveloffset=+2]
+include::modules/hcp-dc-tls-hosted.adoc[leveloffset=+2]
+
+[id="hcp-dc-bm-hosted"]
+== Creating a hosted cluster on bare metal
+
+A hosted cluster is an {product-title} cluster with its control plane and API endpoint hosted on a management cluster. The hosted cluster includes the control plane and its corresponding data plane.
+
+include::modules/hcp-hc-objects.adoc[leveloffset=+2]
+include::modules/hcp-nodepool-hc.adoc[leveloffset=+2]
+include::modules/hcp-dc-infraenv.adoc[leveloffset=+2]
+include::modules/hcp-worker-hc.adoc[leveloffset=+2]
+include::modules/hcp-bm-hosts.adoc[leveloffset=+2]
+include::modules/hcp-dc-scale-np.adoc[leveloffset=+2]

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

@@ -0,0 +1,67 @@
+:_mod-docs-content-type: ASSEMBLY
+[id="hcp-deploy-dc-virt"]
+include::_attributes/common-attributes.adoc[]
+= Deploying {hcp} on {VirtProductName} in a disconnected environment
+:context: hcp-deploy-dc-virt
+
+toc::[]
+
+When you deploy {hcp} in a disconnected environment, some of the steps differ depending on the platform you use. The following procedures are specific to deployments on {VirtProductName}.
+
+:FeatureName: {hcp-capital} on {VirtProductName} in a disconnected environment
+include::snippets/technology-preview.adoc[]
+
+[id="prerequisites_{context}"]
+== Prerequisites
+
+* You have a disconnected {product-title} environment serving as your management cluster.
+* You have an internal registry to mirror images on. For more information, see xref:../../disconnected/mirroring/index.adoc#installing-mirroring-disconnected-about[About disconnected installation mirroring].
+
+include::modules/hcp-dc-image-mirror.adoc[leveloffset=+1]
+include::modules/hcp-dc-apply-objects.adoc[leveloffset=+1]
+
+[role="_additional-resources"]
+.Additional resources
+* xref:../../disconnected/mirroring/installing-mirroring-disconnected.adoc#installing-mirroring-disconnected[Mirroring images for a disconnected installation using the oc-mirror plugin].
+
+[id="hcp-dc-mce-virt"]
+== Deploying {mce-short} for a disconnected installation of {hcp}
+
+The {mce} plays a crucial role in deploying clusters across providers. If you do not have {mce-short} installed, review the following documentation to understand the prerequisites and steps to install it:
+
+* link:https://docs.redhat.com/en/documentation/red_hat_advanced_cluster_management_for_kubernetes/2.11/html/clusters/cluster_mce_overview#mce-intro[About cluster lifecycle with multicluster engine operator]
+* link:https://docs.redhat.com/en/documentation/red_hat_advanced_cluster_management_for_kubernetes/2.11/html/clusters/cluster_mce_overview#mce-install-intro[Installing and upgrading multicluster engine operator]
+
+[id="hcp-dc-tls-virt"]
+== Configuring TLS certificates for a disconnected installation of {hcp}
+
+To ensure proper function in a disconnected deployment, you need to configure the registry CA certificates in the management cluster and the worker nodes for the hosted cluster.
+
+include::modules/hcp-dc-tls-mgmt.adoc[leveloffset=+2]
+include::modules/hcp-dc-tls-hosted.adoc[leveloffset=+2]
+
+[id="hcp-dc-virt-hosted"]
+== Creating a hosted cluster on {VirtProductName}
+
+A hosted cluster is an {product-title} cluster with its control plane and API endpoint hosted on a management cluster. The hosted cluster includes the control plane and its corresponding data plane.
+
+include::modules/hcp-virt-reqs.adoc[leveloffset=+2]
+include::modules/hcp-virt-create-hc-cli.adoc[leveloffset=+2]
+include::modules/hcp-virt-ingress-dns.adoc[leveloffset=+2]
+
+[id="hcp-dc-virt-ingress-dns-custom"]
+=== Customizing ingress and DNS behavior
+
+If you do not want to use the default ingress and DNS behavior, you can configure a KubeVirt hosted cluster with a unique base domain at creation time. This option requires manual configuration steps during creation and involves three main steps: cluster creation, load balancer creation, and wildcard DNS configuration.
+
+include::modules/hcp-virt-hc-base-domain.adoc[leveloffset=+3]
+include::modules/hcp-virt-load-balancer.adoc[leveloffset=+3]
+include::modules/hcp-virt-wildcard-dns.adoc[leveloffset=+3]
+
+[id="hcp-dc-finish"]
+== Finishing the deployment
+
+You can monitor the deployment of a hosted cluster from two perspectives: the control plane and the data plane.
+
+include::modules/hcp-monitor-cp.adoc[leveloffset=+2]
+include::modules/hcp-monitor-dp.adoc[leveloffset=+2]

hosted_control_planes/hcp-disconnected/hcp-deploy-dc-virt.adoc

@@ -0,0 +1,21 @@
+:_mod-docs-content-type: ASSEMBLY
+[id="hcp-deploy-dc"]
+include::_attributes/common-attributes.adoc[]
+= Introduction to {hcp} in a disconnected environment
+:context: hcp-deploy-dc
+
+toc::[]
+
+In the context of {hcp}, a disconnected environment is an {product-title} deployment that is not connected to the internet and that uses {hcp} as a base. You can deploy {hcp} in a disconnected environment on bare metal or {VirtProductName}.
+
+{hcp-capital} in disconnected environments function differently than in standalone {product-title}:
+
+* The control plane is in the management cluster. The control plane is where the pods of the hosted control plane are run and managed by the Control Plane Operator. 
+* The data plane is in the workers of the hosted cluster. The data plane is where the workloads and other pods run, all managed by the HostedClusterConfig Operator.
+
+Depending on where the pods are running, they are affected by the `ImageDigestMirrorSet` (IDMS) or `ImageContentSourcePolicy` (ICSP) that is created in the management cluster or by the `ImageContentSource` that is set in the `spec` field of the manifest for the hosted cluster. The `spec` field is translated into an IDMS object on the hosted cluster.
+
+You can deploy {hcp} in a disconnected environment on IPv4, IPv6, and dual-stack networks. IPv4 is one of the simplest network configurations to deploy {hcp} in a disconnected environment. IPv4 ranges require fewer external components than IPv6 or dual-stack setups. For {hcp} on {VirtProductName} in a disconnected environment, use either an IPv4 or a dual-stack network.
+
+:FeatureName: {hcp-capital} in a disconnected environment on a dual-stack network
+include::snippets/technology-preview.adoc[]

hosted_control_planes/hcp-disconnected/hcp-deploy-dc.adoc

@@ -0,0 +1 @@
+../../images

hosted_control_planes/hcp-disconnected/images

@@ -0,0 +1 @@
+../../modules

hosted_control_planes/hcp-disconnected/modules

@@ -0,0 +1 @@
+../../snippets