Skip to content

Commit 028158b

Browse files
rm3lthemr0c
andcommitted
Apply suggestions from code review
Co-authored-by: Fabrice Flore-Thébault <[email protected]>
1 parent bc5fcf5 commit 028158b

File tree

4 files changed

+15
-25
lines changed

4 files changed

+15
-25
lines changed

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

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,7 @@
1010
* A cluster administrator has installed the {product} Operator.
1111
* You have subscribed to `registry.redhat.io`. For more information, see https://access.redhat.com/RegistryAuthentication[{company-name} Container Registry Authentication].
1212
* You have set the context to the {aks-short} cluster in your current `kubeconfig`. For more information, see https://learn.microsoft.com/en-us/azure/aks/learn/quick-kubernetes-deploy-cli#connect-to-the-cluster[Connect to the cluster].
13-
* You have installed `kubectl`. For more information, see https://learn.microsoft.com/en-us/cli/azure/aks?view=azure-cli-latest#az-aks-install-cli[`az aks install-cli].
13+
* You have installed `kubectl`. For more information, see https://learn.microsoft.com/en-us/cli/azure/aks?view=azure-cli-latest#az-aks-install-cli[`az aks install-cli`].
1414

1515
.Procedure
1616

@@ -135,4 +135,4 @@ kubectl -n <your_namespace> apply -f rhdh.yaml
135135

136136
.Verification
137137

138-
Access the deployed {product-short} using the URL: `https://<app_address>`, where <app_address> is the Ingress address obtained earlier (for example, `https://108.141.70.228`).
138+
Access the deployed {product-short} using the URL: pass:c,a,q[{my-product-url}], where <app_address> is the Ingress address obtained earlier, such as pass:c,a,q[https://108.141.70.228].

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

Lines changed: 5 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -4,27 +4,22 @@
44
[id='proc-rhdh-deploy-aks-operator_{context}']
55
= Deploying {product-short} on {aks-short} with the Operator
66

7-
The {product} Operator installation requires the Operator Lifecycle Manager (OLM) framework.
8-
9-
.Additonal resources
10-
* For information about the OLM, see link:https://olm.operatorframework.io/docs/[Operator Lifecycle Manager(OLM)] documentation.
11-
12-
== Installing the {product-short} Operator with the OLM framework
13-
147
You can install the {product-short} Operator on {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}.
158

9+
== Installing the {product-short} Operator
10+
1611
.Prerequisites
1712

1813
* You have cluster-scoped privileges.
1914
* You have set the context to the {aks-short} cluster in your current `kubeconfig`. For more information, see https://learn.microsoft.com/en-us/azure/aks/learn/quick-kubernetes-deploy-cli#connect-to-the-cluster[Connect to the cluster].
20-
* You have installed `kubectl`. For more information, see https://learn.microsoft.com/en-us/cli/azure/aks?view=azure-cli-latest#az-aks-install-cli[`az aks install-cli].
15+
* You have installed `kubectl`. For more information, see https://learn.microsoft.com/en-us/cli/azure/aks?view=azure-cli-latest#az-aks-install-cli[`az aks install-cli`].
2116
* You have subscribed to `registry.redhat.io`. For more information, see https://access.redhat.com/RegistryAuthentication[{company-name} Container Registry Authentication].
22-
* You have installed the Operator Lifecycle Manager (OLM). For more information about installation and troubleshooting, see https://olm.operatorframework.io/docs/getting-started/[OLM QuickStart] or https://operatorhub.io/how-to-install-an-operator#How-do-I-get-Operator-Lifecycle-Manager?[How do I get Operator Lifecycle Manager?]
17+
* You installed the Operator Lifecycle Manager (OLM) framework. See link:https://olm.operatorframework.io/docs/[Operator Lifecycle Manager(OLM)].
2318

2419
.Procedure
2520

2621
// Procedure fragment on installing the operator using OLM on a non OCP cluster
27-
include::./proc-install-rhdh-operator-olm.adoc[]
22+
include::./snip-install-rhdh-operator-olm.adoc[]
2823

2924
. Modify the default configuration of `db-statefulset.yaml` and `deployment.yaml` by adding the following fragment:
3025
+

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

Lines changed: 4 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -4,27 +4,22 @@
44
[id='proc-rhdh-deploy-eks-operator_{context}']
55
= Installing {product-short} on {eks-short} with the Operator
66

7-
The {product} Operator installation requires the Operator Lifecycle Manager (OLM) framework.
8-
9-
.Additonal resources
10-
* For information about the OLM, see link:https://olm.operatorframework.io/docs/[Operator Lifecycle Manager(OLM)] documentation.
11-
12-
== Installing the {product-short} Operator with the OLM framework
13-
147
You can install the {product-short} Operator on {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}.
158

9+
== Installing the {product-short} Operator
10+
1611
.Prerequisites
1712

1813
* You have cluster-scoped privileges.
1914
* 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].
2015
* You have installed `kubectl`. For more information, see https://docs.aws.amazon.com/eks/latest/userguide/install-kubectl.html[Installing or updating kubectl].
2116
* You have subscribed to `registry.redhat.io`. For more information, see https://access.redhat.com/RegistryAuthentication[{company-name} Container Registry Authentication].
22-
* You have installed the Operator Lifecycle Manager (OLM). For more information about installation and troubleshooting, see https://olm.operatorframework.io/docs/getting-started/[OLM QuickStart] or https://operatorhub.io/how-to-install-an-operator#How-do-I-get-Operator-Lifecycle-Manager?[How do I get Operator Lifecycle Manager?]
17+
* You installed the Operator Lifecycle Manager (OLM) framework. See link:https://olm.operatorframework.io/docs/[Operator Lifecycle Manager(OLM)].
2318

2419
.Procedure
2520

2621
// Procedure fragment on installing the operator using OLM on a non OCP cluster
27-
include::./proc-install-rhdh-operator-olm.adoc[]
22+
include::./snip-install-rhdh-operator-olm.adoc[]
2823

2924
.. Locate the `db-statefulset.yaml` string and add the `fsGroup` to its `spec.template.spec.securityContext`, as shown in the following example:
3025
+

modules/installation/proc-install-rhdh-operator-olm.adoc renamed to modules/installation/snip-install-rhdh-operator-olm.adoc

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -50,7 +50,7 @@ kubectl -n olm get packagemanifests
5050
----
5151
--
5252

53-
. Run the following command in your terminal to create the `rhdh-operator` namespace where the Operator is installed:
53+
. Create the `rhdh-operator` namespace aimed at containing the Operator:
5454
+
5555
--
5656
[source,terminal]
@@ -59,7 +59,7 @@ kubectl create namespace rhdh-operator
5959
----
6060
--
6161

62-
. Create a pull secret in the `rhdh-operator` namespace using the following command:
62+
. Create a pull secret in the `rhdh-operator` namespace:
6363
+
6464
--
6565
[source,terminal]
@@ -92,7 +92,7 @@ EOF
9292
----
9393
--
9494

95-
. Create a `Subscription` resource using the following code:
95+
. Create a `Subscription` resource:
9696
+
9797
--
9898
[source,terminal,subs="attributes+"]
@@ -114,7 +114,7 @@ EOF
114114
----
115115
--
116116

117-
. Run the following command to verify that the created Operator is running:
117+
. Verify that the created Operator is running:
118118
+
119119
--
120120
[source,terminal]

0 commit comments

Comments
 (0)