title: Using VPC connector in Cloud Run
body: <p>I have ended up in a tricky situation regarding the usage of serverless vpc-connectors in Cloud-Run. The service needs to call both other internal(e.g only allow invocation via internal traffic) cloud run services and some external services/urls. Given the two options for routing through the connector, namely (1. Route only traffic to private IPS through the connector) and (2. Route all traffic through the connector), it seems impossible to me to configure the connector in such a way that makes it correctly resolve both external and internal URLs.</p>
  <p>When going with the first option, the URLs for internal cloud run services are not properly resolved but the external ones are. There are no static IPs for cloud-run services so using &quot;internal&quot; IPs is not an option.</p>
  <p>When choosing the second option, the internal URLs are resolved properly but not the external ones.</p>
  <p>Is there a solution to this situation?</p>