DIAGRAMS-484:Updated OSD on GCP arch model diagrams.

modules/osd-private-architecture-model-gcp.adoc

@@ -16,5 +16,5 @@ Red Hat recommends using Private Service Connect (PSC) when deploying a private
 Red Hat SRE management access the cluster through a public load balancer endpoint that are restricted to Red Hat IPs. The API server endpoint is private. A separate Red Hat API server endpoint is public (but restricted to Red Hat trusted IP addresses). The default ingress controller can be public or private. The following image shows network connectivity of a private cluster without Private Service Connect (PSC).
 
 .{product-title} on {GCP} deployed on a private network without PSC
-image::osd_gcp_private_no_psc_arch.png[Private without PSC architecture model]
+image::484_b_Openshift_osd_gcp_private_no_psc_arch_0525.png[Private without PSC architecture model]
 

modules/osd-private-psc-architecture-model-gcp.adoc

@@ -10,4 +10,4 @@ With a private GCP Private Service Connect (PSC) network configuration, your clu
 Red Hat SRE management access the cluster over the GCP PSC-enabled private connectivity. The default ingress controller are private. Additional ingress controllers can be public or private. The following diagram shows network connectivity of a private cluster with PSC.
 
 .{product-title} on {GCP} deployed on a private network with PSC
-image::osd_gcp_private_with_psc_arch.png[Private with PSC architecture model]
+image::484_a_OpenShift_osd_gcp_private_psc_arch_0525.png[Private with PSC architecture model]

modules/osd-public-architecture-model-gcp.adoc

@@ -9,5 +9,5 @@
 With a public network configuration, your cluster API server endpoint and application routes are internet-facing. The default ingress controller can be public or private. The following image shows the network connectivity of a public cluster.
 
 .{product-title} on {GCP} deployed on a public network
-image::osd_gcp_public_arch.png[Public architecture model]
+image::484_c_Openshift_osd_gcp_public_arch_0525.png[Public architecture model]