Merge pull request #90883 from lahinson/ocpbugs-53402-hcp-kcli

[OCPBUGS-53402]: Replacing mentions of kcli from the HCP docs

Author: lahinson

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

@@ -11,10 +11,16 @@ When you provision {hcp} on bare metal, you use the Agent platform. The Agent pl
 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]
+
+[role="_additional-resources"]
+.Additional resources
+* link:https://docs.redhat.com/en/documentation/red_hat_advanced_cluster_management_for_kubernetes/2.13/html/clusters/cluster_mce_overview#mce-install-intro[Installing and upgrading multicluster engine operator]
+* xref:../../hosted_control_planes/hcp-prepare/hcp-enable-disable.html#hcp-enable-manual-addon_hcp-enable-disable[Manually enabling the hypershift-addon managed cluster add-on for local-cluster]
+* link:https://docs.redhat.com/en/documentation/red_hat_advanced_cluster_management_for_kubernetes/2.13/html/clusters/cluster_mce_overview#mce-intro[About cluster lifecycle with multicluster engine operator]
+
 include::modules/hcp-dc-web-server.adoc[leveloffset=+1]
 include::modules/hcp-dc-image-mirror.adoc[leveloffset=+1]
 
@@ -27,17 +33,9 @@ include::modules/hcp-dc-apply-objects.adoc[leveloffset=+1]
 
 [role="_additional-resources"]
 .Additional resources
-* xref:../../disconnected/mirroring/about-installing-oc-mirror-v2.adoc#about-installing-oc-mirror-v2[Mirroring images for a disconnected installation by using the oc-mirror plugin v2].
+* xref:../../disconnected/mirroring/about-installing-oc-mirror-v2.adoc#about-installing-oc-mirror-v2[Mirroring images for a disconnected installation by using the oc-mirror plugin v2]
 
-[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.13/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.13/html/clusters/cluster_mce_overview#mce-install-intro[Installing and upgrading multicluster engine operator]
-
-include::modules/hcp-agentserviceconfig.adoc[leveloffset=+2]
+include::modules/hcp-agentserviceconfig.adoc[leveloffset=+1]
 
 [id="hcp-dc-tls-bm"]
 == Configuring TLS certificates for a disconnected installation of {hcp}
@@ -55,6 +53,11 @@ A hosted cluster is an {product-title} cluster with its control plane and API en
 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]
+
+[role="_additional-resources"]
+.Additional resources
+* xref:../../installing/installing_bare_metal/upi/scaling-a-user-provisioned-cluster-with-the-bare-metal-operator.adoc#upi-provisioning-new-hosts-in-a-upi-cluster_scaling-a-user-provisioned-cluster-with-the-bare-metal-operator[Provisioning new hosts in a user-provisioned cluster by using the BMO]
+* xref:../../nodes/pods/nodes-pods-secrets.adoc#nodes-pods-secrets-about_nodes-pods-secrets[Understanding secrets]
+
 include::modules/hcp-dc-scale-np.adoc[leveloffset=+2]

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

@@ -25,7 +25,7 @@ include::modules/hcp-dc-apply-objects.adoc[leveloffset=+1]
 
 [role="_additional-resources"]
 .Additional resources
-* xref:../../disconnected/mirroring/about-installing-oc-mirror-v2.adoc#about-installing-oc-mirror-v2[Mirroring images for a disconnected installation by using the oc-mirror plugin v2].
+* xref:../../disconnected/mirroring/about-installing-oc-mirror-v2.adoc#about-installing-oc-mirror-v2[Mirroring images for a disconnected installation by using the oc-mirror plugin v2]
 
 [id="hcp-dc-mce-virt"]
 == Deploying {mce-short} for a disconnected installation of {hcp}

modules/hcp-agentserviceconfig.adoc

@@ -121,4 +121,4 @@ assisted-service-668b49548-9m7xw                       2/2     Running   5
 
 .Next steps
 
-Configure TLS certificates by completing the steps in _Configuring TLS certificates for a disconnected installation of {hcp}_.
+Configure TLS certificates.

modules/hcp-bm-hosts.adoc

@@ -10,13 +10,15 @@ A _bare metal host_ is an `openshift-machine-api` object that encompasses physic
 
 .Prerequisites
 
-Before you create the bare metal host and destination nodes, you must have the destination machines ready.
+* Before you create the bare metal host and destination nodes, you must have the destination machines ready.
+
+* You have installed a {op-system-first} compute machine on bare-metal infrastructure for use in the cluster.
 
 .Procedure
 
 To create a bare metal host, complete the following steps:
 
-. Create a YAML file with the following information:
+. Create a YAML file with the following information. For more information about what details to enter for the bare metal host, see "Provisioning new hosts in a user-provisioned cluster by using the BMO".
 +
 Because you have at least one secret that holds the bare metal host credentials, you need to create at least two objects for each worker node.
 +
@@ -25,31 +27,31 @@ Because you have at least one secret that holds the bare metal host credentials,
 apiVersion: v1
 kind: Secret
 metadata:
-  name: <hosted_cluster_name>-worker0-bmc-secret \// <1>
-  namespace: <hosted_cluster_namespace>-<hosted_cluster_name> \// <2>
+  name: <hosted_cluster_name>-worker0-bmc-secret # <1>
+  namespace: <hosted_cluster_namespace>-<hosted_cluster_name> # <2>
 data:
-  password: YWRtaW4= \// <3>
-  username: YWRtaW4= \// <4>
+  password: YWRtaW4= # <3>
+  username: YWRtaW4= # <4>
 type: Opaque
 # ...
 apiVersion: metal3.io/v1alpha1
 kind: BareMetalHost
 metadata:
   name: <hosted_cluster_name>-worker0
-  namespace: <hosted_cluster_namespace>-<hosted_cluster_name> \// <2>
+  namespace: <hosted_cluster_namespace>-<hosted_cluster_name> # <2>
   labels:
-    infraenvs.agent-install.openshift.io: <hosted_cluster_name> \// <5>
+    infraenvs.agent-install.openshift.io: <hosted_cluster_name> # <5>
   annotations:
     inspect.metal3.io: disabled
-    bmac.agent-install.openshift.io/hostname: <hosted_cluster_name>-worker0 \// <6>
+    bmac.agent-install.openshift.io/hostname: <hosted_cluster_name>-worker0 # <6>
 spec:
-  automatedCleaningMode: disabled \// <7>
+  automatedCleaningMode: disabled # <7>
   bmc:
-    disableCertificateVerification: true \// <8>
-    address: redfish-virtualmedia://[192.168.126.1]:9000/redfish/v1/Systems/local/<hosted_cluster_name>-worker0 \// <9>
-    credentialsName: <hosted_cluster_name>-worker0-bmc-secret \// <10>
-  bootMACAddress: aa:aa:aa:aa:02:11 \// <11>
-  online: true // <12>
+    disableCertificateVerification: true # <8>
+    address: redfish-virtualmedia://[192.168.126.1]:9000/redfish/v1/Systems/local/<hosted_cluster_name>-worker0 # <9>
+    credentialsName: <hosted_cluster_name>-worker0-bmc-secret # <10>
+  bootMACAddress: aa:aa:aa:aa:02:11 # <11>
+  online: true # <12>
 ----
 +
 <1> Replace `<hosted_cluster_name>` with your hosted cluster.

modules/hcp-dc-hypervisor.adoc

@@ -40,17 +40,6 @@ mirror:
       type: ocp
     kubeVirtContainer: true <2>
     graph: true
-  additionalImages: <3>
-  - name: quay.io/karmab/origin-keepalived-ipfailover:latest
-  - name: quay.io/karmab/kubectl:latest
-  - name: quay.io/karmab/haproxy:latest
-  - name: quay.io/karmab/mdns-publisher:latest
-  - name: quay.io/karmab/origin-coredns:latest
-  - name: quay.io/karmab/curl:latest
-  - name: quay.io/karmab/kcli:latest
-  - name: quay.io/user-name/trbsht:latest
-  - name: quay.io/user-name/hypershift:BMSelfManage-v{product-version}
-  - name: registry.redhat.io/openshift4/ose-kube-rbac-proxy:v4.10
   operators:
   - catalog: registry.redhat.io/redhat/redhat-operator-index:v{product-version}
     packages:
@@ -61,13 +50,12 @@ mirror:
     - name: mcg-operator
     - name: ocs-operator
     - name: metallb-operator
-    - name: kubevirt-hyperconverged <4>
+    - name: kubevirt-hyperconverged <3>
 ----
 +
 <1> Replace `<4.x.y-build>` with the supported {product-title} version you want to use.
 <2> Set this optional flag to `true` if you want to also mirror the container disk image for the {op-system-first} boot image for the KubeVirt provider. This flag is available with oc-mirror v2 only.
-<3> Images specified in the `additionalImages` field are examples only and are not strictly needed.
-<4> For deployments that use the KubeVirt provider, include this line.
+<3> For deployments that use the KubeVirt provider, include this line.
 
 . Start the mirroring process by entering the following command:
 +