RHIDP-1923 - GKE: Document how RHDH can be installed in GKE

Author: Gerry-Forde

modules/installation/proc-deploy-rhdh-instance-gke.adoc

@@ -20,6 +20,7 @@ You need to create an `A` record with the value equal to the IP address. This ca
 . Create a ConfigMap named `app-config-rhdh` containing the {product-short} configuration using the following template:
 +
 --
+.`app-config-rhdh.yaml` fragment
 [source,yaml,subs="attributes+"]
 ----
 apiVersion: v1
@@ -47,6 +48,7 @@ data:
 . Create a Secret named `secrets-rhdh` and add a key named `BACKEND_SECRET` with a `Base64-encoded` string as value:
 +
 --
+.`secrets-rhdh` fragment
 [source,yaml]
 ----
 apiVersion: v1
@@ -85,6 +87,7 @@ kubectl patch serviceaccount default \
 . Create a Custom Resource file using the following template:
 +
 --
+.Custom Resource fragment
 [source,yaml,subs="attributes+"]
 ----
 apiVersion: rhdh.redhat.com/v1alpha1
@@ -110,6 +113,7 @@ spec:
 . Set up a Google-managed certificate by creating a `ManagedCertificate` object which you must attach to the Ingress.
 +
 --
+. Example of a `ManagedCertificate` object
 [source,yaml,subs="attributes+"]
 ----
 apiVersion: networking.gke.io/v1
@@ -126,6 +130,7 @@ For more information about setting up a Google-managed certificate, see https://
 . Create a `FrontendConfig` object to set a policy for redirecting to HTTPS. You must attach this policy to the Ingress. 
 +
 --
+. Example of a `FrontendConfig` object
 [source,yaml,subs="attributes+"]
 ----
 apiVersion: networking.gke.io/v1beta1
@@ -143,6 +148,7 @@ For more information about setting a policy to redirect to HTTPS, see https://cl
 . Create an ingress resource using the following template, customizing the names as needed:
 +
 --
+.Example of an ingress resource configuration
 [source,yaml,subs="attributes+"]
 ----
 apiVersion: networking.k8s.io/v1

modules/installation/proc-rhdh-deploy-gke-helm.adoc

@@ -52,6 +52,7 @@ The created pull secret is used to pull the {product-short} images from the {com
 . Set up a Google-managed certificate by creating a `ManagedCertificate` object that you must attach to the ingress.
 +
 --
+.Example of attaching a `ManagedCertificate` object to the ingress
 [source,yaml,subs="attributes+"]
 ----
 apiVersion: networking.gke.io/v1
@@ -68,6 +69,7 @@ For more information about setting up a Google-managed certificate, see https://
 . Create a `FrontendConfig` object to set a policy for redirecting to HTTPS. You must attach this policy to the ingress. 
 +
 --
+.Example of attaching a `FrontendConfig` object to the ingress
 [source,yaml,subs="attributes+"]
 ----
 apiVersion: networking.gke.io/v1beta1
@@ -130,27 +132,6 @@ helm -n <your_namespace> install -f values.yaml <your_deploy_name> \
 +
 For the latest Helm Chart version, see this https://github.com/openshift-helm-charts/charts/tree/main/charts/redhat/redhat/redhat-developer-hub[Helm Charts] repository.
 +
-////
-. Confirm that the deployment is complete.
-+
-[source,terminal,subs="attributes+"]
-----
-kubectl get deploy <you_deploy_name>-developer-hub -n <your_namespace>
-----
-
-. Verify that the service and ingress were created.
-+
-[source,terminal,subs="attributes+"]
-----
-kubectl get service -n <your_namespace>
-kubectl get ingress -n <your_namespace>
-----
-+
-[NOTE]
-Wait for the `ManagedCertificate` to be provisioned. This can take a couple of hours.
-
-. Access {product-very-short} with `https://<rhdh_domain_name>`
-////
 
 [NOTE]
 --
@@ -159,7 +140,6 @@ Wait for the `ManagedCertificate` to be provisioned. This can take a couple of h
 [source,terminal,subs="attributes+"]
 ----
 helm -n <your_namespace> upgrade -f values.yaml <your_deploy_name> openshift-helm-charts/redhat-developer-hub --version <UPGRADE_CHART_VERSION>
-
 ----
 
 * To delete your deployment, use the following command:
@@ -169,6 +149,7 @@ helm -n <your_namespace> upgrade -f values.yaml <your_deploy_name> openshift-hel
 helm -n <your_namespace> delete <your_deploy_name>
 ----
 --
+
 .Verification
 * Confirm that the deployment is complete.
 +

modules/installation/proc-rhdh-deploy-gke-operator.adoc

@@ -148,6 +148,7 @@ kubectl -n rhdh-operator edit configmap backstage-default-config
 .. Locate the `db-statefulset.yaml` string and add the `fsGroup` to its `spec.template.spec.securityContext`, as shown in the following example:
 +
 --
+.`db-statefulset.yaml` fragment
 [source,yaml]
 ----
   db-statefulset.yaml: |
@@ -169,6 +170,7 @@ kubectl -n rhdh-operator edit configmap backstage-default-config
 .. Locate the `deployment.yaml` string and add the `fsGroup` to its specification, as shown in the following example:
 +
 --
+.`deployment.yaml` fragment
 [source,yaml]
 ----
   deployment.yaml: |
@@ -187,6 +189,7 @@ kubectl -n rhdh-operator edit configmap backstage-default-config
 .. Locate the `service.yaml` string and change the `type` to `NodePort` as follows:
 +
 --
+.`service.yaml` fragment
 [source,yaml]
 ----
   service.yaml: |