Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions modules/installation/proc-rhdh-deploy-aks-operator.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -8,6 +8,7 @@ You can deploy your {product-short} on {aks-short} using the {product} Operator.

.Procedure

////
. 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:
+
--
Expand Down Expand Up @@ -39,6 +40,7 @@ kubectl apply -f rhdh-operator-<VERSION>.yaml
Execution of the previous command is cluster-scoped and requires appropriate cluster privileges.
====
--
////

. 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:
+
Expand Down
70 changes: 1 addition & 69 deletions modules/installation/proc-rhdh-deploy-eks-operator.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -127,72 +127,4 @@ kubectl -n rhdh-operator patch deployment \
--type=merge
----
====
--

. Update the default configuration of the operator to ensure that {product-short} resources can start correctly in {eks-short} using the following steps:
.. Edit the `backstage-default-config` ConfigMap in the `rhdh-operator` namespace using the following command:
+
--
[source,terminal]
----
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:
+
--
[source,yaml]
----
db-statefulset.yaml: |
apiVersion: apps/v1
kind: StatefulSet
--- TRUNCATED ---
spec:
--- TRUNCATED ---
restartPolicy: Always
securityContext:
# You can assign any random value as fsGroup
fsGroup: 2000
serviceAccount: default
serviceAccountName: default
--- TRUNCATED ---
----
--

.. Locate the `deployment.yaml` string and add the `fsGroup` to its specification, as shown in the following example:
+
--
[source,yaml]
----
deployment.yaml: |
apiVersion: apps/v1
kind: Deployment
--- TRUNCATED ---
spec:
securityContext:
# You can assign any random value as fsGroup
fsGroup: 3000
automountServiceAccountToken: false
--- TRUNCATED ---
----
--

.. Locate the `service.yaml` string and change the `type` to `NodePort` as follows:
+
--
[source,yaml]
----
service.yaml: |
apiVersion: v1
kind: Service
spec:
# NodePort is required for the ALB to route to the Service
type: NodePort
--- TRUNCATED ---
----
--

.. Save and exit.
+
Wait for a few minutes until the changes are automatically applied to the operator pods.
--
73 changes: 1 addition & 72 deletions modules/installation/proc-rhdh-deploy-gke-operator.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -136,75 +136,4 @@ kubectl -n rhdh-operator patch deployment \
--type=merge
----
====
--

. Update the default configuration of the Operator to ensure that {product-short} resources can start correctly in {gke-short} using the following steps:
.. Edit the `backstage-default-config` ConfigMap in the `rhdh-operator` namespace using the following command:
+
--
[source,terminal]
----
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: |
apiVersion: apps/v1
kind: StatefulSet
--- TRUNCATED ---
spec:
--- TRUNCATED ---
restartPolicy: Always
securityContext:
# You can assign any random value as fsGroup
fsGroup: 2000
serviceAccount: default
serviceAccountName: default
--- TRUNCATED ---
----
--

.. 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: |
apiVersion: apps/v1
kind: Deployment
--- TRUNCATED ---
spec:
securityContext:
# You can assign any random value as fsGroup
fsGroup: 3000
automountServiceAccountToken: false
--- TRUNCATED ---
----
--

.. Locate the `service.yaml` string and change the `type` to `NodePort` as follows:
+
--
.`service.yaml` fragment
[source,yaml]
----
service.yaml: |
apiVersion: v1
kind: Service
spec:
# NodePort is required for the ALB to route to the Service
type: NodePort
--- TRUNCATED ---
----
--

.. Save and exit.
+
Wait until the changes are automatically applied to the Operator pods.
--