Refactoring to reuse common steps

Signed-off-by: Fabrice Flore-Thébault <[email protected]>

Author: themr0c

assemblies/assembly-installing-rhdh-on-aks-by-using-the-operator.adoc

@@ -0,0 +1,11 @@
+:_mod-docs-content-type: ASSEMBLY
+
+[id="assembly-install-rhdh-eks-operator"]
+= Installing {product-short} on {aks-brand-name} by using the Operator
+
+The {product} Operator installation requires the Operator Lifecycle Manager (OLM) framework.
+
+include::modules/installation/proc-installing-the-operator-on-aks-by-using-olm.adoc[leveloffset=+1]
+
+include::modules/installation/proc-running-rhdh-on-aks-by-using-the-operator.adoc[leveloffset=+1]
+

…/assembly-install-rhdh-eks-operator.adoc …g-rhdh-on-eks-by-using-the-operator.adocassemblies/assembly-install-rhdh-eks-operator.adoc renamed to assemblies/assembly-installing-rhdh-on-eks-by-using-the-operator.adoc assemblies/assembly-install-rhdh-eks-operator.adoc renamed to assemblies/assembly-installing-rhdh-on-eks-by-using-the-operator.adoc

@@ -5,8 +5,7 @@
 
 The {product} Operator installation requires the Operator Lifecycle Manager (OLM) framework.
 
-include::modules/installation/proc-rhdh-deploy-eks-operator.adoc[leveloffset=+1]
+include::modules/installation/proc-installing-the-operator-on-eks-by-using-olm.adoc[leveloffset=+1]
 
-.Additional resources
-* link:https://olm.operatorframework.io/docs/[Operator Lifecycle Manager(OLM)]
+include::modules/installation/proc-running-rhdh-on-eks-by-using-the-operator.adoc[leveloffset=+1]
 

modules/installation/proc-installing-the-operator-on-aks-by-using-olm.adoc

@@ -0,0 +1,13 @@
+:_mod-docs-content-type: PROCEDURE
+
+[id="proc-rhdh-deploy-aks-operator_{context}"]
+= Installing the {product} operator on {aks-brand-name} by using the OLM framework
+
+You can install the {product-short} Operator on {aks-brand-name} ({aks-short}) by using the https://olm.operatorframework.io[Operator Lifecycle Manager (OLM) framework].
+Then, you can proceed to deploy your {product-short} instance in {aks-short}.
+
+.Prerequisites
+include::snip-installing-the-operator-common-prerequisites.adoc[]
+
+.Procedure
+include::snip-installing-the-operator-common-steps.adoc[]

modules/installation/proc-installing-the-operator-on-eks-by-using-olm.adoc

@@ -0,0 +1,16 @@
+:_mod-docs-content-type: PROCEDURE
+
+[id="proc-installing-the-operator-on-eks-by-using-olm_{context}"]
+= Installing the {product-short} Operator on {eks-brand-name} by using the OLM framework
+
+You can install the {product-short} Operator on {eks-brand-name} ({eks-short}) using the https://olm.operatorframework.io[Operator Lifecycle Manager (OLM) framework].
+Following that, you can proceed to deploy your {product-short} instance in {eks-short}.
+
+.Prerequisites
+* You have set the context to the {eks-short} cluster in your current `kubeconfig`.
+For more information, see https://docs.aws.amazon.com/eks/latest/userguide/create-kubeconfig.html[Creating or updating a kubeconfig file for an Amazon {eks-short} cluster].
+
+include::snip-installing-the-operator-common-prerequisites.adoc[]
+
+.Procedure
+include::snip-installing-the-operator-common-steps.adoc[]

modules/installation/proc-installing-the-operator-on-gke-by-using-olm.adoc

@@ -0,0 +1,23 @@
+:_mod-docs-content-type: PROCEDURE
+
+[id="proc-installing-the-operator-by-using-olm_{context}"]
+= Installing the {product-short} Operator on {gke-brand-name} by using the OLM framework
+
+You can install the {product-short} Operator on {gke-brand-name} ({gke-short}) by using the https://olm.operatorframework.io[Operator Lifecycle Manager (OLM) framework].
+Following that, you can proceed to deploy your {product-short} instance in {gke-short}.
+
+.Prerequisites
+* You have logged in to your Google account and created a https://cloud.google.com/kubernetes-engine/docs/how-to/creating-an-autopilot-cluster[GKE Autopilot] or https://cloud.google.com/kubernetes-engine/docs/how-to/creating-a-zonal-cluster[GKE Standard] cluster.
+
+include::snip-installing-the-operator-common-prerequisites.adoc[]
+
+.Procedure
+. Connect to your GKE cluster:
++
+[source,terminal]
+----
+$ gcloud container clusters get-credentials <cluster-name> --location=<cluster-location>
+----
+_<cluster-name>_:: Enter your GKE cluster name.
+_<cluster-location>_:: Enter your GKE cluster location.
+include::snip-installing-the-operator-common-steps.adoc[]

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

@@ -1,10 +1,11 @@
 :_mod-docs-content-type: PROCEDURE
 
+
 [id="proc-rhdh-deploy-aks-operator_{context}"]
 = Deploying {product-short} on {aks-short} with the Operator
 
 You can install the {product-short} Operator on {aks-brand-name} ({aks-short}) using the https://olm.operatorframework.io[Operator Lifecycle Manager (OLM) framework].
-Following that, you can proceed to deploy your {product-short} instance in {aks-short}.
+Then, you can proceed to deploy your {product-short} instance in {aks-short}.
 
 For information about the OLM, see link:https://olm.operatorframework.io/docs/[Operator Lifecycle Manager(OLM)] documentation.
 
@@ -21,18 +22,23 @@ For more information, see https://kubernetes.io/docs/tasks/tools/#kubectl[Instal
 * Your system meets the link:https://docs.redhat.com/en/documentation/red_hat_developer_hub/1.7/html-single/about_red_hat_developer_hub/index#rhdh-sizing_about-rhdh[sizing requirements for {product}].
 
 .Procedure
-. 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:
+. Create the `rhdh-operator` namespace that will contain the {product} Operator:
 +
---
-[source,bash]
+[source,terminal]
 ----
-kubectl -n <your_namespace> create secret docker-registry rhdh-pull-secret \
+$ kubectl create namespace rhdh-operator
+----
+
+. Create a pull secret using your {company-name} credentials to access images from the protected {company-name} registry:
++
+[source,terminal]
+----
+$ kubectl -n rhdh-operator create secret docker-registry rhdh-pull-secret \
     --docker-server=registry.redhat.io \
     --docker-username=<redhat_user_name> \
     --docker-password=<redhat_password> \
     --docker-email=<email>
 ----
---
 
 . Create an Ingress manifest file, named `rhdh-ingress.yaml`, specifying your {product-short} service name as follows:
 +

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

@@ -1,7 +1,7 @@
 :_mod-docs-content-type: PROCEDURE
 
-[id="proc-deploy-rhdh-instance-eks.adoc_{context}"]
-= Deploying the {product-short} instance on {eks-short} with the Operator
+[id="proc-running-rhdh-on-eks-by-using-the-operator_{context}"]
+= Running {product} on {eks-brand-name} by using the Operator
 
 .Prerequisites