Question

A development team deploys a Cloud Run service that must call a backend running on a Compute Engine VM addressed only by its internal RFC 1918 IP inside a custom-mode VPC. The team wants the lowest-latency egress path with the least infrastructure to manage and the ability to scale out without provisioning a fixed pool of connector instances. Which configuration should they choose?

Accepted Answer

Enable Direct VPC egress on the Cloud Run service, attaching it to the target subnet in the VPC

Answer

Create a Serverless VPC Access connector sized with a fixed min/max instance range and route egress through it

Answer

Configure a Private Service Connect endpoint pointing at the VM's internal IP and route Cloud Run traffic to it

Answer

Deploy Cloud NAT and set the Cloud Run service egress to route all traffic through the NAT gateway