Skip to content

List all hostnames used when loading GitLab.com

Harsh Chouraria requested to merge hchouraria-doc-gitlabcom-hostnames-list into master

What does this MR do?

Administrators of tightly controlled environments may require a list of domain names to place in their allow-lists of proxies to permit their users to access all of GitLab.com pages and features.

This documentation addition next to the IP range section can help such admins by acting as a single source list of all domains to permit when electing to use GitLab.com in their org.

Note: I think the infrastructure group may be relevant here as they may be aware of all the domains in use and their entire purposes, but I could not find a group::infrastructure label existing. So, I've added the generic infrastructure label I found available instead.

Related issues

Author's checklist (required)

Do not add the feature, frontend, backend, ~"bug", or database labels if you are only updating documentation. These labels will cause the MR to be added to code verification QA issues.

When applicable:

Review checklist

All reviewers can help ensure accuracy, clarity, completeness, and adherence to the Documentation Guidelines and Style Guide.

1. Primary Reviewer

  • Review by a code reviewer or other selected colleague to confirm accuracy, clarity, and completeness. This can be skipped for minor fixes without substantive content changes.

2. Technical Writer

  • Technical writer review. If not requested for this MR, must be scheduled post-merge. To request for this MR, assign the writer listed for the applicable DevOps stage.

For more information about labels, see Technical Writing workflows - Labels.

For suggestions that you are confident don't need to be reviewed, change them locally and push a commit directly to save others from unneeded reviews. For example:

  • Clear typos, like this is a typpo.
  • Minor issues, like single quotes instead of double quotes, Oxford commas, and periods.

For more information, see our documentation on Merging a merge request.

3. Maintainer

  1. Review by assigned maintainer, who can always request/require the above reviews. Maintainer's review can occur before or after a technical writer review.
  2. Ensure a release milestone is set.
  3. If there has not been a technical writer review, create an issue for one using the Doc Review template.

Merge request reports