Question

A development team uses Cloud Build to run their CI/CD pipelines. Their build steps need to run integration tests against a Cloud SQL instance and a Memorystore instance that are only reachable through private IP addresses inside their VPC. The default Cloud Build workers cannot reach these private resources. As the architect, what should you advise the team to implement so the builds can connect to the private resources with the least operational overhead?

Accepted Answer

Configure a Cloud Build private pool (private worker pool) with a peered VPC connection to the team's network so build workers can reach the private IP resources.

Answer

Assign external IP addresses to the Cloud SQL and Memorystore instances and restrict access with authorized networks pointing at Cloud Build IP ranges.

Answer

Run a self-managed Jenkins server on a Compute Engine VM inside the VPC and migrate all pipelines off Cloud Build.

Answer

Create a Serverless VPC Access connector and attach it to the default Cloud Build worker pool to route traffic into the VPC.