Skip to content

Add AWS EKS-specific instructions in Quick Start

Mitchell Nielsen requested to merge add-eks-quickstart-docs into master

What does this MR do?

Replaces !1852 (closed).

When I installed on AWS EKS, I encountered two problems:

  • I used a Fargate cluster, and that did not set up the ingress correctly--use EC2
  • On EKS, the ingress ADDRESSes are URLs, not IP addresses

I explained these things.

Questions to address from !1852 (comment 1054536186):

Does it make sense to interweave the complexity of multiple providers into a single quick-start?

My personal opinion is yes, given how pervasive AWS EKS is. Additionally, there are EKS-specific considerations that are worth mentioning. We want to ensure as many as possible who work through the quickstart guide end up with a successful deployment for customer delight.

Does the message of the entire document read clearly?

I believe so, and we can get reviewer feedback on this as well.

Are there any steps required, which are not currently present?

Confirming with testing by following the instructions.

  • GitLab application accessible
  • Able to log in
  • Able to create a new project
  • Able to upload a screenshot in an issue
  • Able to access MinIO application
  • All certificates issued correctly
  • All pods up and running as expected

✅

Related issues

None.

Checklist

See Definition of done.

For anything in this list which will not be completed, please provide a reason in the MR discussion.

Required

  • Merge Request Title and Description are up to date, accurate, and descriptive
  • MR targeting the appropriate branch
  • MR has a green pipeline on GitLab.com

Expected (please provide an explanation if not completing)

  • Test plan indicating conditions for success has been posted and passes
  • Documentation created/updated
  • Tests added
  • Integration tests added to GitLab QA
  • Equivalent MR/issue for omnibus-gitlab opened
Edited by Mitchell Nielsen

Merge request reports