Hi,
In order to let dataform repo connect to our self-managed gitlab, I have to set gitlab server's firewall rule to allow any source ip(CIDR=0.0.0.0/0), it's really not good way.
Does Dataform connect git has fixed ip list? Or only support gitlab.com?
Solved! Go to Solution.
Hi there,
Today, private instances would need to be exposed to the public web, through an IP or hostname. By Q2, we’ll provide a stable subnet address range for all of our egress traffic that customers can allowlist in their instance’s firewall.
Hi there,
Today, private instances would need to be exposed to the public web, through an IP or hostname. By Q2, we’ll provide a stable subnet address range for all of our egress traffic that customers can allowlist in their instance’s firewall.
Hi ghh,
Got it. Thanks for your explain.
Looking forward to more improvement in the future!
Hi, Can you share the list of all yours subnet address range for all of egress traffic
@ghh " By Q2, we’ll provide a stable subnet address range for all of our egress traffic that customers can allowlist in their instance’s firewall. " - Just wondering if this response from you is still the case and if you can share the list of the subnet address range for all egress traffic from Dataform? I am still not finding any documentation on this.
UPDATE:
Found out through GCP support that the egress IP range list is an 'experimental' workaround and that's why there is no documentation on it. However I was able to fill out a form provided by the support member to join a waitlist where eventually GCP support will provide me a range of those IP address.
They did mention the experimental range of IPs is only available for us-central1 and europe-west4 regions. Also that in 2024 this will probably need replaced with network peering solution they are rolling out to services.