Question

Your team's Cloud Build pipeline runs integration tests that must connect to a Cloud SQL instance and internal microservices that only have private IP addresses inside a VPC. The default Cloud Build workers cannot reach these private resources, and security policy prohibits exposing the database or services to public IPs. You need the build's integration test step to successfully reach the private resources with minimal ongoing maintenance. What should you do?

Accepted Answer

Configure a Cloud Build private pool with a peered network connection to your VPC, and run the integration test step in that private pool.

Answer

Assign a public IP to the Cloud SQL instance and use authorized networks to allow the Cloud Build worker IP ranges.

Answer

Deploy a Cloud VPN tunnel from the default Cloud Build worker pool to your VPC and route test traffic through it.

Answer

Add a startup step that installs the Cloud SQL Auth Proxy on the default pool and hardcode the private IP of each microservice.