-
Task
-
Resolution: Done
-
Normal
-
None
-
None
After a meeting with the Ansible team who were stuck trying to install a Helm-based RHDH on EKS, we identified the following possible improvements to our EKS docs:
- They found the links to the AWS docs to be a bit too generalized, with no specific steps. Not sure what we should do about that.
- Clarify the prerequisites for a working EKS cluster
- I noticed that their EKS cluster did not have any node group, which is needed for workloads to be scheduled. Maybe we could link the first prerequisite to the AWS documentation on how to create an EKS cluster or clarify that a node group is required: https://docs.aws.amazon.com/eks/latest/userguide/getting-started-console.html
- The default storage class needs to work for Persistent Volumes to be able to be provisioned. We could link to Use Amazon EBS Storage (tested) and/or Use Amazon EFS Storage (not tested)
- It was unclear how the hosted zone entry in Route53 links to the RHDH instance. We need to clarify that installing RHDH would result in a new Application Load Balancer provisioned by AWS with a DNS name, which needs to be used as an alias in the Route53 record.
(This could be a separate issue). Their ultimate goal was to try out their Ansible plugins in EKS. They mentioned https://issues.redhat.com/browse/RHIDP-1624?focusedId=24344226&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-24344226 as a way for them to serve their plugins on OpenShift (which they are using on ROSA), but they want to have similar doc for non-OpenShift clusters like EKS. This might be temporary until RHIDP-2534 is delivered.
UPDATE: Perform the following actions:
- Add a prerequisite in the Operator and Helm install docs that a working default storage class, like the EBS storage add-on, is needed in the EKS cluster.
- In the procedures, right after the Ingress creation (after step 5 for the Operator, and after Step 4 for Helm), we could mention that EKS would provision an Application Load Balancer (ALB) with an IP, which the required domain name would need to be updated to point to.
1.
|
[DOC] Technical Review |
|
Closed | |
Armel Soro |
2.
|
[DOC] Peer Review |
|
Closed | |
Jana Vrbkova |