Modifying installation initializing module for private and xpn

Author: bscott-rh

installing/installing_gcp/installing-gcp-shared-vpc.adoc

@@ -52,8 +52,6 @@ include::modules/installation-gcp-managing-dns-solution.adoc[leveloffset=+2]
 .Additional resources
 * xref:../../installing/installing_gcp/installation-config-parameters-gcp.adoc#installation-config-parameters-gcp[Installation configuration parameters for {gcp-first}]
 
-include::modules/installation-gcp-shared-vpc-config.adoc[leveloffset=+2]
-
 include::modules/installation-gcp-config-yaml-simple.adoc[leveloffset=+2]
 
 [role="_additional-resources"]

modules/installation-gcp-shared-vpc-config.adoc

@@ -127,6 +127,33 @@ $ mkdir <installation_directory>
 You must create a directory. Some installation assets, such as bootstrap X.509 certificates have short expiration intervals, so you must not reuse an installation directory. If you want to reuse individual files from another cluster installation, you can copy them into your directory. However, the file names for the installation assets might change between releases. Use caution when copying installation files from an earlier {product-title} version.
 ====
 
+ifdef::gcp-private[]
+. Edit the `install-config.yaml` file to set the `publish: Internal` parameter.
+endif::gcp-private[]
+ifdef::gcp-shared[]
+. Edit the `install-config.yaml` file to set the parameters necessary for installation into a shared VPC.
+.. Define the network, subnets, and project names for the shared VPC:
++
+[source,yaml]
+----
+# ...
+platform:
+  gcp:
+    computeSubnet: <shared_vpc_compute_subnet>
+    controlPlaneSubnet: <shared_vpc_control_plane_subnet>
+    network: <shared_vpc_name>
+    networkProjectID: <host_project_name>
+    projectID: <service_project_name>
+----
+where:
+
+`<shared_vpc_compute_subnet>`:: Specifies the name of the subnet in the shared VPC for compute machines to use.
+`<shared_vpc_control_plane_subnet>`:: Specifies the name of the subnet in the shared VPC for control plane machines to use.
+`<shared_vpc_name>`:: Specifies the name of the shared VPC.
+`<host_project_name>`:: Specifies the name of the host project where the shared VPC exists.
+`<service_project_name>`:: Specifies the name of the project where you want to install the cluster.
+endif::gcp-shared[]
+
 . Customize the provided sample `install-config.yaml` file template and save the file in the `<installation_directory>`.
 ifdef::ibm-cloud-restricted[]
 +

modules/installation-initializing-manual.adoc

@@ -587,9 +587,11 @@ ifdef::gcp+restricted[]
 +
 [source,yaml]
 ----
-network: <existing_vpc>
-controlPlaneSubnet: <control_plane_subnet>
-computeSubnet: <compute_subnet>
+platform:
+  gcp:
+    network: <existing_vpc>
+    controlPlaneSubnet: <control_plane_subnet>
+    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.

modules/installation-initializing.adoc

@@ -6,7 +6,8 @@
 [id="private-clusters-about-gcp_{context}"]
 = Private clusters in {gcp-short}
 
-To create a private cluster on {gcp-first}, you must provide an existing private VPC and subnets to host the cluster. The installation program must also be able to resolve the DNS records that the cluster requires. The installation program configures the Ingress Operator and API server for only internal traffic.
+[role="_abstract"]
+To create a private cluster on {gcp-first}, you must provide an existing private VPC and subnets to host the cluster, and you must specify `publish: Internal` in your `install-config.yaml` file. The installation program must also be able to resolve the DNS records that the cluster requires. The installation program configures the Ingress Operator and API server for only internal traffic.
 
 The cluster still requires access to internet to access the {gcp-short} APIs.