RHIDP-3219: Improve docs for installing on EKS with Helm (#1594)

* Improve docs for installing on EKS with Helm

* Improve docs for installing on EKS with Helm

* Improve docs for installing on EKS with Helm

* Improve docs for installing on EKS with Helm

* Improve docs for installing on EKS with Helm

* Improve docs for installing on EKS with Helm

* Improve docs for installing on EKS with Helm

* Update with new suggestions

---------

Co-authored-by: GitHub Actions <[email protected]>

Author: jmagak

modules/configuring/proc-using-the-operator-to-run-rhdh-with-your-custom-configuration.adoc

@@ -12,6 +12,7 @@ To use the {product-short} Operator to run {product} with your custom configurat
 * By using the {platform-cli-link}, you have access, with developer permissions, to the {platform} cluster aimed at containing your {product-short} instance.
 * Your administrator has installed the {product} Operator in the cluster.
 * You have provisioned your custom config maps and secrets in your `_<{my-product-namespace}>_` project.
+* You have a working default storage class, such as the EBS storage add-on, configured in your {eks-short} cluster.
 
 .Procedure
 . Author your {product-custom-resource-type} CR in a `{my-product-cr-name}.yaml` file to use your custom config maps and secrets.

modules/installation/proc-exposing-your-operator-based-rhdh-instance-on-eks.adoc

@@ -50,6 +50,8 @@ EOF
 +
 Replace pass:c,a,q[{my-product-domain}] with your {product-short} domain name and update the value of `alb.ingress.kubernetes.io/certificate-arn` with your certificate ARN.
 
+. Update your required domain name, (for example, in Route 53 or your external DNS service) to point to the provisioned IP address. {eks-name} provisions an Application Load Balancer (ALB) with a corresponding IP address.
+
 . To deploy the created Ingress, run:
 +
 [source,terminal,subs="+attributes"]

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

@@ -14,6 +14,7 @@ When you install the {product-short} Helm chart in {eks-name} ({eks-short}), it
 * 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].
 * You have installed `kubectl`. For more information, see https://docs.aws.amazon.com/eks/latest/userguide/install-kubectl.html[Installing or updating kubectl].
 * You have installed Helm 3 or the latest. For more information, see https://docs.aws.amazon.com/eks/latest/userguide/helm.html[Using Helm with Amazon {eks-short}].
+* You have a working default storage class, such as the EBS storage add-on, configured in your {eks-short} cluster.
 * Make sure that your system meets the minimum sizing requirements. See {about-book-link}#rhdh-sizing_about-rhdh[Sizing requirements for {product}].
 
 .Procedure
@@ -106,6 +107,8 @@ upstream:
   volumePermissions:
     enabled: true
 ----
+. Update your required domain name, (for example, in Route 53 or your external DNS service) to point to the provisioned IP address. {eks-name} provisions an Application Load Balancer (ALB) with a corresponding IP address.
+
 . Run the following command in your terminal to deploy {product-short} using the latest version of Helm Chart and using the values.yaml file created in the previous step:
 +
 [source,terminal,subs="attributes+"]