Merge pull request #51678 from mjpytlak/osdocs-3520

OSDOCS-3520: Adding steps to deploy with a GCP Marketplace image

Author: mjpytlak

installing/installing_gcp/installing-gcp-customizations.adoc

@@ -36,24 +36,28 @@ include::modules/installation-gcp-tested-machine-types.adoc[leveloffset=+2]
 include::modules/installation-gcp-config-yaml.adoc[leveloffset=+2]
 
 [role="_additional-resources"]
-== Additional resources
+.Additional resources
 
 * xref:../../machine_management/creating_machinesets/creating-machineset-gcp.adoc#machineset-enabling-customer-managed-encryption_creating-machineset-gcp[Enabling customer-managed encryption keys for a compute machine set]
 
 include::modules/installation-configure-proxy.adoc[leveloffset=+2]
 
+include::modules/installation-gcp-marketplace.adoc[leveloffset=+1]
+
 include::modules/installation-launching-installer.adoc[leveloffset=+1]
 
 include::modules/cli-installing-cli.adoc[leveloffset=+1]
 
 include::modules/cli-logging-in-kubeadmin.adoc[leveloffset=+1]
 
+[role="_additional-resources"]
 .Additional resources
 
 * See xref:../../web_console/web-console.adoc#web-console[Accessing the web console] for more details about accessing and understanding the {product-title} web console.
 
 include::modules/cluster-telemetry.adoc[leveloffset=+1]
 
+[role="_additional-resources"]
 .Additional resources
 
 * See xref:../../support/remote_health_monitoring/about-remote-health-monitoring.adoc#about-remote-health-monitoring[About remote health monitoring] for more information about the Telemetry service

modules/installation-creating-gcp-worker.adoc

@@ -111,7 +111,7 @@ EOF
 <2> `infra_id` is the `INFRA_ID` infrastructure name from the extraction step.
 <3> `zone` is the zone to deploy the worker machine into, for example `us-central1-a`.
 <4> `compute_subnet` is the `selfLink` URL to the compute subnet.
-<5> `image` is the `selfLink` URL to the {op-system} image.
+<5> `image` is the `selfLink` URL to the {op-system} image. To deploy using a GCP Marketplace image, specify `image: \https://www.googleapis.com/compute/v1/projects/redhat-marketplace-public/global/images/redhat-coreos-ocp-48-x86-64-202210040145`.
 <6> `machine_type` is the machine type of the instance, for example `n1-standard-4`.
 <7> `service_account_email` is the email address for the worker service account that you created.
 <8> `ignition` is the contents of the `worker.ign` file.

modules/installation-gcp-marketplace.adoc

@@ -0,0 +1,44 @@
+// Module included in the following assemblies:
+//
+// * installing/installing_gcp/installing-gcp-customizations.adoc
+
+:_content-type: PROCEDURE
+[id="installation-gcp-marketplace_{context}"]
+= Using a GCP Marketplace image
+If you want to deploy an {product-title} cluster using a GCP Marketplace image, you must create the manifests and edit the compute machine set definitions to specify the GCP Marketplace image.
+
+.Prerequisites
+
+* You have the {product-title} installation program and the pull secret for your cluster.
+
+.Procedure
+
+. Generate the installation manifests by running the following command:
++
+[source,terminal]
+----
+$ openshift-install create manifests --dir <installation_dir>
+----
+
+. Locate the following files:
+
+** `<installation_dir>/openshift/99_openshift-cluster-api_worker-machineset-0.yaml`
+** `<installation_dir>/openshift/99_openshift-cluster-api_worker-machineset-1.yaml`
+** `<installation_dir>/openshift/99_openshift-cluster-api_worker-machineset-2.yaml`
+
+. In each file, edit the `.spec.template.spec.providerSpec.value.disks[0].image` property to `projects/redhat-marketplace-public/global/images/redhat-coreos-ocp-48-x86-64-202210040145`.
+
+.Example compute machine set with the GCP Marketplace image
+[source,yaml]
+----
+deletionProtection: false
+disks:
+- autoDelete: true
+  boot: true
+  image: projects/redhat-marketplace-public/global/images/redhat-coreos-ocp-48-x86-64-202210040145
+  labels: null
+  sizeGb: 128
+  type: pd-ssd
+kind: GCPMachineProviderSpec
+machineType: n2-standard-4
+----