Skip to content

Commit 1464556

Browse files
committed
RHIDP-1923 - GKE: Document how RHDH can be installed in GKE
1 parent 61585d8 commit 1464556

File tree

3 files changed

+12
-22
lines changed

3 files changed

+12
-22
lines changed

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

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -20,6 +20,7 @@ You need to create an `A` record with the value equal to the IP address. This ca
2020
. Create a ConfigMap named `app-config-rhdh` containing the {product-short} configuration using the following template:
2121
+
2222
--
23+
.`app-config-rhdh.yaml` fragment
2324
[source,yaml,subs="attributes+"]
2425
----
2526
apiVersion: v1
@@ -47,6 +48,7 @@ data:
4748
. Create a Secret named `secrets-rhdh` and add a key named `BACKEND_SECRET` with a `Base64-encoded` string as value:
4849
+
4950
--
51+
.`secrets-rhdh` fragment
5052
[source,yaml]
5153
----
5254
apiVersion: v1
@@ -85,6 +87,7 @@ kubectl patch serviceaccount default \
8587
. Create a Custom Resource file using the following template:
8688
+
8789
--
90+
.Custom Resource fragment
8891
[source,yaml,subs="attributes+"]
8992
----
9093
apiVersion: rhdh.redhat.com/v1alpha1
@@ -110,6 +113,7 @@ spec:
110113
. Set up a Google-managed certificate by creating a `ManagedCertificate` object which you must attach to the Ingress.
111114
+
112115
--
116+
. Example of a `ManagedCertificate` object
113117
[source,yaml,subs="attributes+"]
114118
----
115119
apiVersion: networking.gke.io/v1
@@ -126,6 +130,7 @@ For more information about setting up a Google-managed certificate, see https://
126130
. Create a `FrontendConfig` object to set a policy for redirecting to HTTPS. You must attach this policy to the Ingress.
127131
+
128132
--
133+
. Example of a `FrontendConfig` object
129134
[source,yaml,subs="attributes+"]
130135
----
131136
apiVersion: networking.gke.io/v1beta1
@@ -143,6 +148,7 @@ For more information about setting a policy to redirect to HTTPS, see https://cl
143148
. Create an ingress resource using the following template, customizing the names as needed:
144149
+
145150
--
151+
.Example of an ingress resource configuration
146152
[source,yaml,subs="attributes+"]
147153
----
148154
apiVersion: networking.k8s.io/v1

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

Lines changed: 3 additions & 22 deletions
Original file line numberDiff line numberDiff line change
@@ -52,6 +52,7 @@ The created pull secret is used to pull the {product-short} images from the {com
5252
. Set up a Google-managed certificate by creating a `ManagedCertificate` object that you must attach to the ingress.
5353
+
5454
--
55+
.Example of attaching a `ManagedCertificate` object to the ingress
5556
[source,yaml,subs="attributes+"]
5657
----
5758
apiVersion: networking.gke.io/v1
@@ -68,6 +69,7 @@ For more information about setting up a Google-managed certificate, see https://
6869
. Create a `FrontendConfig` object to set a policy for redirecting to HTTPS. You must attach this policy to the ingress.
6970
+
7071
--
72+
.Example of attaching a `FrontendConfig` object to the ingress
7173
[source,yaml,subs="attributes+"]
7274
----
7375
apiVersion: networking.gke.io/v1beta1
@@ -130,27 +132,6 @@ helm -n <your_namespace> install -f values.yaml <your_deploy_name> \
130132
+
131133
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.
132134
+
133-
////
134-
. Confirm that the deployment is complete.
135-
+
136-
[source,terminal,subs="attributes+"]
137-
----
138-
kubectl get deploy <you_deploy_name>-developer-hub -n <your_namespace>
139-
----
140-
141-
. Verify that the service and ingress were created.
142-
+
143-
[source,terminal,subs="attributes+"]
144-
----
145-
kubectl get service -n <your_namespace>
146-
kubectl get ingress -n <your_namespace>
147-
----
148-
+
149-
[NOTE]
150-
Wait for the `ManagedCertificate` to be provisioned. This can take a couple of hours.
151-
152-
. Access {product-very-short} with `https://<rhdh_domain_name>`
153-
////
154135

155136
[NOTE]
156137
--
@@ -159,7 +140,6 @@ Wait for the `ManagedCertificate` to be provisioned. This can take a couple of h
159140
[source,terminal,subs="attributes+"]
160141
----
161142
helm -n <your_namespace> upgrade -f values.yaml <your_deploy_name> openshift-helm-charts/redhat-developer-hub --version <UPGRADE_CHART_VERSION>
162-
163143
----
164144

165145
* 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
169149
helm -n <your_namespace> delete <your_deploy_name>
170150
----
171151
--
152+
172153
.Verification
173154
* Confirm that the deployment is complete.
174155
+

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

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -148,6 +148,7 @@ kubectl -n rhdh-operator edit configmap backstage-default-config
148148
.. Locate the `db-statefulset.yaml` string and add the `fsGroup` to its `spec.template.spec.securityContext`, as shown in the following example:
149149
+
150150
--
151+
.`db-statefulset.yaml` fragment
151152
[source,yaml]
152153
----
153154
db-statefulset.yaml: |
@@ -169,6 +170,7 @@ kubectl -n rhdh-operator edit configmap backstage-default-config
169170
.. Locate the `deployment.yaml` string and add the `fsGroup` to its specification, as shown in the following example:
170171
+
171172
--
173+
.`deployment.yaml` fragment
172174
[source,yaml]
173175
----
174176
deployment.yaml: |
@@ -187,6 +189,7 @@ kubectl -n rhdh-operator edit configmap backstage-default-config
187189
.. Locate the `service.yaml` string and change the `type` to `NodePort` as follows:
188190
+
189191
--
192+
.`service.yaml` fragment
190193
[source,yaml]
191194
----
192195
service.yaml: |

0 commit comments

Comments
 (0)