Egress traffic from gitlab.com should come from a known list of IPs
Promoted to epic: &97
Currently the ephemeral nature of our GCP infrastructure makes it rather difficult for the security minded to open the appropriate firewall rules for the GitLab.com infrastructure egress traffic.
Utilize this issue to see what we can do to ease this burden.
Example: https://cloud.google.com/vpc/docs/special-configurations#multiple-natgateways
Reference: https://gitlab.com/gitlab-com/gl-infra/infrastructure/issues/434
When complete, need to update IP range documentation