summaryrefslogtreecommitdiff
path: root/doc/user/gitlab_com
diff options
context:
space:
mode:
authorGitLab Bot <gitlab-bot@gitlab.com>2022-09-13 00:10:14 +0000
committerGitLab Bot <gitlab-bot@gitlab.com>2022-09-13 00:10:14 +0000
commit7e87cfd402a5faba6e1287e150702ca51156eac4 (patch)
treeff2e46a3a91cf013d8930c6e8a5ba5e3cdf39330 /doc/user/gitlab_com
parent3b69a04945341516a2ed6a291769c50fe04336df (diff)
downloadgitlab-ce-7e87cfd402a5faba6e1287e150702ca51156eac4.tar.gz
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'doc/user/gitlab_com')
-rw-r--r--doc/user/gitlab_com/index.md6
1 files changed, 3 insertions, 3 deletions
diff --git a/doc/user/gitlab_com/index.md b/doc/user/gitlab_com/index.md
index 9bb79b5cc90..62b685ea4f4 100644
--- a/doc/user/gitlab_com/index.md
+++ b/doc/user/gitlab_com/index.md
@@ -208,9 +208,9 @@ from those IPs and allow them.
GitLab.com is fronted by Cloudflare. For incoming connections to GitLab.com, you might need to allow CIDR blocks of Cloudflare ([IPv4](https://www.cloudflare.com/ips-v4/) and [IPv6](https://www.cloudflare.com/ips-v6/)).
-For outgoing connections from CI/CD runners, we are not providing static IP
-addresses. All GitLab.com shared runners are deployed into Google Cloud Platform (GCP). Any
-IP-based firewall can be configured by looking up all
+For outgoing connections from CI/CD runners, we are not providing static IP addresses.
+All GitLab.com shared runners are deployed into Google Cloud Platform (GCP) in `us-east1`.
+Any IP-based firewall can be configured by looking up
[IP address ranges or CIDR blocks for GCP](https://cloud.google.com/compute/docs/faq#find_ip_range).
## Hostname list