Commit e035a2e9 authored by Achilleas Pipinellis's avatar Achilleas Pipinellis

Merge branch 'hp-ip_range' into 'master'

Provide ip-range for whitelisting

See merge request gitlab-org/gitlab!27315
parents f4cf5d32 0b73c60a
...@@ -88,11 +88,14 @@ or over the size limit, you can [reduce your repository size with Git](../projec ...@@ -88,11 +88,14 @@ or over the size limit, you can [reduce your repository size with Git](../projec
## IP range ## IP range
GitLab.com, CI/CD, and related services are deployed into Google Cloud Platform (GCP). Any GitLab.com is using the IP range `34.74.90.64/28` for traffic from its Web/API
IP based firewall can be configured by looking up all fleet. You can expect connections from webhooks or repository mirroring to come
[IP address ranges or CIDR blocks for GCP](https://cloud.google.com/compute/docs/faq#where_can_i_find_product_name_short_ip_ranges). from those IPs and whitelist them.
[Static endpoints](https://gitlab.com/groups/gitlab-com/gl-infra/-/epics/97) are being considered. For connections from CI/CD runners we are not providing static IP addresses.
All our runners are deployed into Google Cloud Platform (GCP) - any IP based
firewall can be configured by looking up all
[IP address ranges or CIDR blocks for GCP](https://cloud.google.com/compute/docs/faq#where_can_i_find_product_name_short_ip_ranges).
## Maximum number of webhooks ## Maximum number of webhooks
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment