Skip to content

Commit e8e7ba8

Browse files
openshift-cherrypick-robotGerry-Fordehmanwani-rh
authored
RHIDP-5612 - Fix platform related documentation for Operator (#1260)
Co-authored-by: Gerry-Forde <[email protected]> Co-authored-by: Heena Manwani <[email protected]>
1 parent 35e2b39 commit e8e7ba8

File tree

3 files changed

+4
-141
lines changed

3 files changed

+4
-141
lines changed

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

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -8,6 +8,7 @@ You can deploy your {product-short} on {aks-short} using the {product} Operator.
88

99
.Procedure
1010

11+
////
1112
. Obtain the {product} Operator manifest file, named `rhdh-operator-<VERSION>.yaml`, and modify the default configuration of `db-statefulset.yaml` and `deployment.yaml` by adding the following fragment:
1213
+
1314
--
@@ -39,6 +40,7 @@ kubectl apply -f rhdh-operator-<VERSION>.yaml
3940
Execution of the previous command is cluster-scoped and requires appropriate cluster privileges.
4041
====
4142
--
43+
////
4244

4345
. Create an `ImagePull Secret` named `rhdh-pull-secret` using your Red Hat credentials to access images from the protected `registry.redhat.io` as shown in the following example:
4446
+

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

Lines changed: 1 addition & 69 deletions
Original file line numberDiff line numberDiff line change
@@ -121,72 +121,4 @@ kubectl -n rhdh-operator patch deployment \
121121
--type=merge
122122
----
123123
====
124-
--
125-
126-
. Update the default configuration of the operator to ensure that {product-short} resources can start correctly in {eks-short} using the following steps:
127-
.. Edit the `backstage-default-config` ConfigMap in the `rhdh-operator` namespace using the following command:
128-
+
129-
--
130-
[source,terminal]
131-
----
132-
kubectl -n rhdh-operator edit configmap backstage-default-config
133-
----
134-
--
135-
136-
.. Locate the `db-statefulset.yaml` string and add the `fsGroup` to its `spec.template.spec.securityContext`, as shown in the following example:
137-
+
138-
--
139-
[source,yaml]
140-
----
141-
db-statefulset.yaml: |
142-
apiVersion: apps/v1
143-
kind: StatefulSet
144-
--- TRUNCATED ---
145-
spec:
146-
--- TRUNCATED ---
147-
restartPolicy: Always
148-
securityContext:
149-
# You can assign any random value as fsGroup
150-
fsGroup: 2000
151-
serviceAccount: default
152-
serviceAccountName: default
153-
--- TRUNCATED ---
154-
----
155-
--
156-
157-
.. Locate the `deployment.yaml` string and add the `fsGroup` to its specification, as shown in the following example:
158-
+
159-
--
160-
[source,yaml]
161-
----
162-
deployment.yaml: |
163-
apiVersion: apps/v1
164-
kind: Deployment
165-
--- TRUNCATED ---
166-
spec:
167-
securityContext:
168-
# You can assign any random value as fsGroup
169-
fsGroup: 3000
170-
automountServiceAccountToken: false
171-
--- TRUNCATED ---
172-
----
173-
--
174-
175-
.. Locate the `service.yaml` string and change the `type` to `NodePort` as follows:
176-
+
177-
--
178-
[source,yaml]
179-
----
180-
service.yaml: |
181-
apiVersion: v1
182-
kind: Service
183-
spec:
184-
# NodePort is required for the ALB to route to the Service
185-
type: NodePort
186-
--- TRUNCATED ---
187-
----
188-
--
189-
190-
.. Save and exit.
191-
+
192-
Wait for a few minutes until the changes are automatically applied to the operator pods.
124+
--

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

Lines changed: 1 addition & 72 deletions
Original file line numberDiff line numberDiff line change
@@ -136,75 +136,4 @@ kubectl -n rhdh-operator patch deployment \
136136
--type=merge
137137
----
138138
====
139-
--
140-
141-
. Update the default configuration of the Operator to ensure that {product-short} resources can start correctly in {gke-short} using the following steps:
142-
.. Edit the `backstage-default-config` ConfigMap in the `rhdh-operator` namespace using the following command:
143-
+
144-
--
145-
[source,terminal]
146-
----
147-
kubectl -n rhdh-operator edit configmap backstage-default-config
148-
----
149-
--
150-
151-
.. Locate the `db-statefulset.yaml` string and add the `fsGroup` to its `spec.template.spec.securityContext`, as shown in the following example:
152-
+
153-
--
154-
.`db-statefulset.yaml` fragment
155-
[source,yaml]
156-
----
157-
db-statefulset.yaml: |
158-
apiVersion: apps/v1
159-
kind: StatefulSet
160-
--- TRUNCATED ---
161-
spec:
162-
--- TRUNCATED ---
163-
restartPolicy: Always
164-
securityContext:
165-
# You can assign any random value as fsGroup
166-
fsGroup: 2000
167-
serviceAccount: default
168-
serviceAccountName: default
169-
--- TRUNCATED ---
170-
----
171-
--
172-
173-
.. Locate the `deployment.yaml` string and add the `fsGroup` to its specification, as shown in the following example:
174-
+
175-
--
176-
.`deployment.yaml` fragment
177-
[source,yaml]
178-
----
179-
deployment.yaml: |
180-
apiVersion: apps/v1
181-
kind: Deployment
182-
--- TRUNCATED ---
183-
spec:
184-
securityContext:
185-
# You can assign any random value as fsGroup
186-
fsGroup: 3000
187-
automountServiceAccountToken: false
188-
--- TRUNCATED ---
189-
----
190-
--
191-
192-
.. Locate the `service.yaml` string and change the `type` to `NodePort` as follows:
193-
+
194-
--
195-
.`service.yaml` fragment
196-
[source,yaml]
197-
----
198-
service.yaml: |
199-
apiVersion: v1
200-
kind: Service
201-
spec:
202-
# NodePort is required for the ALB to route to the Service
203-
type: NodePort
204-
--- TRUNCATED ---
205-
----
206-
--
207-
208-
.. Save and exit.
209-
+
210-
Wait until the changes are automatically applied to the Operator pods.
139+
--

0 commit comments

Comments
 (0)