Hybrid pools overview

This page gives an overview of Cloud Build hybrid pools. If you're new to Cloud Build, read Cloud Build overview.

By default Cloud Build runs its workloads in a fully-managed environment. Hybrid pools enable you to execute Cloud Build workloads anywhere that you can run Kubernetes, using the Anthos platform, such as Google Cloud, on-premises, or other public clouds.

Architecture and compatibility

Hybrid pools extend Cloud Build using an open source Kubernetes framework called Tekton. Using Tekton allows Google Cloud application operators to avoid vendor lock-in and retain Kubernetes features for executing CI/CD workloads. For example, this framework includes capabilities like self-healing, graceful failovers and no single point of failure.

Using hybrid pools

You can set up hybrid pools without many changes to your existing Cloud Build workflows and syntax. You can specify the hybrid worker pool for builds in your existing Cloud Build configuration files.


Once Cloud Build hybrid pools have been set up, you have the ability to maintain oversight across connected environments, all in one place. Google Cloud's control plane enables you to monitor and scale your CI/CD infrastructure as needed on-premises, in Google Cloud, and across your other Kubernetes clusters registered with Anthos.

Hybrid pools retain connectivity using Connect. Hybrid pools support zero-touch updates through the control plane, reducing the overhead to operate at scale.


You can view build history and logs for builds run in the hybrid pool using Google Cloud Console. Hybrid pool logs are also available in Cloud Logging for advanced querying.