You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently in our docs one of the resources we ask users to increase their quota is In-use IP addresses. Because Dataflow is able to use private IP addresses (see use_public_ips) we might be able to remove this limitation. In that case we can use private IP addresses by default.
The only issue we need to verify is that you have to have "enable private google access" enabled on the GCP network or it's enabled by default.
With Private Google Access, VMs that have only internal IP addresses can access select public IPs for Google Cloud and services.
Jobs that access APIs and services outside of Google Cloud require internet access. For example, Python SDK jobs need access to the Python Package Index (PyPI).
Has the use of a NAT gatework with gcp-variant-transforms been tested?
I tried using --use_public_ips false from the pipeline runner (after enabling Private Google Access) and ran into the problem @samanvp noted above - PyPI access failed:
WARNING: Retrying (Retry(total=4, connect=None, read=None, redirect=None, status=None)) after connection
broken by 'ConnectTimeoutError(<pip._vendor.urllib3.connection.VerifiedHTTPSConnection object at
0x7fa88eb5f6d0>, 'Connection to pypi.org timed out. (connect timeout=15)')': /simple/nose/
We are submitting a request for more in-use public IP address quota.
However our current use is for the annotations pipeline. I didn't see any setting of usePrivateAddress so it looks like the setting of use_public_ips is not propagated there.
Currently in our docs one of the resources we ask users to increase their quota is
In-use IP addresses
. Because Dataflow is able to use private IP addresses (seeuse_public_ips
) we might be able to remove this limitation. In that case we can use private IP addresses by default.The only issue we need to verify is that you have to have "enable private google access" enabled on the GCP network or it's enabled by default.
This was suggessted by @kemp-google during #624 review.
The text was updated successfully, but these errors were encountered: