Which option is used by Google Cloud Deploy and Cloud Build to run CI/CD pipelines in customer VPCs?

The option used by Google Cloud Deploy and Cloud Build to run CI/CD pipelines in customer VPCs is private pools. Private pools allow the execution of CI/CD workloads in a secure and isolated manner within a customer's Virtual Private Cloud (VPC). This setup is essential for organizations that require their build and deployment processes to remain within their own network environment for compliance, security, or performance reasons.

Private pools facilitate the provisioning of dedicated resources for workloads, enhancing control over where and how builds are executed, thereby aligning with enterprise security policies and requirements. By utilizing private pools, users can leverage the benefits of Google Cloud's automation tools while maintaining their infrastructure's integrity.

On the other hand, shared pools and hybrid pools serve different purposes within Google Cloud. Shared pools are intended for jobs that can run on Google’s managed environments across various users and projects, lacking the isolation that private pools provide. Hybrid pools may utilize resources across both on-premises and cloud environments but do not specify a focus on executing pipelines within customer VPCs. Tekton, on the other hand, is an open-source framework for creating CI/CD systems, but it is not specific to Google Cloud’s private execution contexts.