Removes Creating a disconnected registry and moves one section to Disconnected Installation mirroring

Author: Steven Smith

installing/installing_bare_metal_ipi/ipi-install-installation-workflow.adoc

@@ -65,6 +65,18 @@ include::modules/ipi-install-configuring-raid-for-worker-node.adoc[leveloffset=+
 
 include::modules/ipi-install-creating-a-disconnected-registry.adoc[leveloffset=+1]
 
+[discrete]
+[id="prerequisites_ipi-disconnected-registry"]
+=== Prerequisites
+
+* If you have already prepared a mirror registry for xref:../../installing/disconnected_install/installing-mirroring-installation-images.adoc#prerequisites_installing-mirroring-installation-images[Mirroring images for a disconnected installation], you can skip directly to xref:../../installing/installing_bare_metal_ipi/ipi-install-installation-workflow.adoc#ipi-modify-install-config-for-a-disconnected-registry_ipi-install-installation-workflow[Modify the install-config.yaml file to use the disconnected registry].
+
+include::modules/ipi-install-preparing-a-disconnected-registry.adoc[leveloffset=+2]
+
+include::modules/ipi-install-mirroring-for-disconnected-registry.adoc[leveloffset=+2]
+
+include::modules/ipi-modify-install-config-for-a-disconnected-registry.adoc[leveloffset=+2]
+
 include::modules/ipi-install-validation-checklist-for-installation.adoc[leveloffset=+1]
 
 include::modules/ipi-install-deploying-the-cluster-via-the-openshift-installer.adoc[leveloffset=+1]

modules/installation-bare-metal-config-yaml.adoc

@@ -303,7 +303,7 @@ ifdef::openshift-origin[]
 endif::openshift-origin[]
 endif::ibm-z,ibm-z-kvm[]
 ifdef::ibm-z,ibm-z-kvm[]
-<14> Add the `additionalTrustBundle` parameter and value. The value must be the contents of the certificate file that you used for your mirror registry, which can be an existing, trusted certificate authority or the self-signed certificate that you generated for the mirror registry.
+<14> Add the `additionalTrustBundle` parameter and value. The value must be the contents of the certificate file that you used for your mirror registry. The certificate file can be an existing, trusted certificate authority or the self-signed certificate that you generated for the mirror registry.
 endif::ibm-z,ibm-z-kvm[]
 ifndef::openshift-origin[]
 <15> Provide the `imageContentSources` section from the output of the command to mirror the repository.

modules/installation-generate-aws-user-infra-install-config.adoc

@@ -68,7 +68,7 @@ This field is optional.
 endif::[]
 
 ifdef::restricted[]
-. Edit the `install-config.yaml` file to provide the additional information that
+. Edit the `install-config.yaml` file to give the additional information that
 is required for an installation in a restricted network.
 .. Update the `pullSecret` value to contain the authentication information for
 your registry:
@@ -82,7 +82,7 @@ For `<local_registry>`, specify the registry domain name, and optionally the
 port, that your mirror registry uses to serve content. For example
 `registry.example.com` or `registry.example.com:5000`. For `<credentials>`,
 specify the base64-encoded user name and password for your mirror registry.
-.. Add the `additionalTrustBundle` parameter and value. The value must be the contents of the certificate file that you used for your mirror registry, which can be an existing, trusted certificate authority or the self-signed certificate that you generated for the mirror registry.
+.. Add the `additionalTrustBundle` parameter and value. The value must be the contents of the certificate file that you used for your mirror registry. The certificate file can be an existing, trusted certificate authority or the self-signed certificate that you generated for the mirror registry.
 +
 [source,yaml]
 ----

modules/installation-initializing.adoc

@@ -485,7 +485,7 @@ platform:
 ----
 endif::vsphere+restricted[]
 ifdef::restricted[]
-. Edit the `install-config.yaml` file to provide the additional information that
+. Edit the `install-config.yaml` file to give the additional information that
 is required for an installation in a restricted network.
 .. Update the `pullSecret` value to contain the authentication information for
 your registry:
@@ -509,7 +509,7 @@ additionalTrustBundle: |
   -----END CERTIFICATE-----
 ----
 +
-The value must be the contents of the certificate file that you used for your mirror registry, which can be an existing, trusted certificate authority or the self-signed certificate that you generated for the mirror registry.
+The value must be the contents of the certificate file that you used for your mirror registry. The certificate file can be an existing, trusted certificate authority, or the self-signed certificate that you generated for the mirror registry.
 
 ifdef::aws+restricted[]
 .. Define the subnets for the VPC to install the cluster in:
@@ -535,7 +535,7 @@ computeSubnet: <compute_subnet>
 For `platform.gcp.network`, specify the name for the existing Google VPC. For `platform.gcp.controlPlaneSubnet` and `platform.gcp.computeSubnet`, specify the existing subnets to deploy the control plane machines and compute machines, respectively.
 endif::gcp+restricted[]
 
-.. Add the image content resources, which look like this excerpt:
+.. Add the image content resources, which resemble the following YAML excerpt:
 +
 [source,yaml]
 ----
@@ -548,7 +548,7 @@ imageContentSources:
   source: registry.example.com/ocp/release
 ----
 +
-To complete these values, use the `imageContentSources` that you recorded during mirror registry creation.
+For these values, use the `imageContentSources` that you recorded during mirror registry creation.
 
 . Make any other modifications to the `install-config.yaml` file that you require. You can find more information about
 the available parameters in the *Installation configuration parameters* section.