Suggest use of AWS Network Load Balancer
What does this MR do?
The note from 2 years ago via gitlab-foss!28030 (merged) uses the older terminology (pre-2016) when it references Elastic Load Balancers (ELBs) where it means Classic Load Balancers (CLBs) based on https://docs.aws.amazon.com/elasticloadbalancing/latest/classic/ DocumentHistory.html
Furthermore, the suggestion of using Application Load Balancer (ALBs) is not the best option anymore since it does not work for TCP based load balancing.
TCP based load balancing is required in self-managed instances to be able to support SSH based authentication to git repositories, which ALBs cannot support.
Going by the matrix we link to, NLB appears to be a better choice: https://aws.amazon.com/elasticloadbalancing/features/#compare
Related issues
Customer ticket: https://gitlab.zendesk.com/agent/tickets/243275
Author's checklist
-
Consider taking the GitLab Technical Writing Fundamentals course -
Follow the: -
Ensure that the product tier badge is added to topic's h1
. -
Request a review based on: - The documentation page's metadata.
- The associated Technical Writer.
If you are only adding documentation, do not add any of the following labels:
~"feature"
~"frontend"
~"backend"
~"bug"
~"database"
These labels cause the MR to be added to code verification QA issues.
Review checklist
Documentation-related MRs should be reviewed by a Technical Writer for a non-blocking review, based on Documentation Guidelines and the Style Guide.
-
If the content requires it, ensure the information is reviewed by a subject matter expert. - Technical writer review items:
-
Ensure docs metadata is present and up-to-date. -
Ensure the appropriate labels are added to this MR. - If relevant to this MR, ensure content topic type principles are in use, including:
-
The headings should be something you'd do a Google search for. Instead of Default behavior
, say something likeDefault behavior when you close an issue
. -
The headings (other than the page title) should be active. Instead of Configuring GDK
, say something likeConfigure GDK
. -
Any task steps should be written as a numbered list. - If the content still needs to be edited for topic types, you can create a follow-up issue with the docs-technical-debt label.
-
-
-
Review by assigned maintainer, who can always request/require the above reviews. Maintainer's review can occur before or after a technical writer review. -
Ensure a release milestone is set.