[[["易于理解","easyToUnderstand","thumb-up"],["解决了我的问题","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["很难理解","hardToUnderstand","thumb-down"],["信息或示例代码不正确","incorrectInformationOrSampleCode","thumb-down"],["没有我需要的信息/示例","missingTheInformationSamplesINeed","thumb-down"],["翻译问题","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["最后更新时间 (UTC)：2025-09-04。"],[[["\u003cp\u003ePrivate pools provide a dedicated, customizable build environment, unlike the default pool, offering enhanced control over aspects like network access and resource allocation.\u003c/p\u003e\n"],["\u003cp\u003ePrivate pools are fully managed by Cloud Build, automatically scaling up and down to zero, eliminating the need for manual infrastructure management.\u003c/p\u003e\n"],["\u003cp\u003ePrivate pools offer greater customization, including the ability to peer into a VPC or shared VPC, utilize VPC Service Controls, and set static internal IP ranges.\u003c/p\u003e\n"],["\u003cp\u003eBuilds within private pools have the flexibility to access resources across different Google Cloud projects, and the maximum concurrent build capacity can be 100 or more, whereas default pools are limited to 30.\u003c/p\u003e\n"],["\u003cp\u003ePrivate pools allow the build to be run in the specified private pool region, and it can be created, updated, and deleted through various tools like API, Google Cloud CLI, Google Cloud console, or infrastructure provisioning tools.\u003c/p\u003e\n"]]],[],null,["# Private pools overview\n\nThis page gives an overview of **private pools** and explains its features.\nIf you're new to Cloud Build, read [Cloud Build overview](/build/docs/overview).\n\nOverview of default pools and private pools\n-------------------------------------------\n\nBy default, when you run a build on Cloud Build, the build runs in a\nsecure, hosted environment with access to the public internet. Each build runs on\nits own **worker** and is isolated from other workloads. You can customize your\nbuild in multiple ways including increasing the size of the machine type or\nallocating more disk space. The default pool has limits on how much you\ncan customize the environment, particularly around private network access.\n\n**Private pools** are private, dedicated pools of workers that offer greater\ncustomization over the build environment, including the ability to access resources\nin a private network. Private pools, similar to default pools, are hosted and\nfully-managed by Cloud Build and scale up and down to zero, with no\ninfrastructure to set up, upgrade, or scale. Because private pools are\ncustomer-specific resources, you can configure them in more ways.\n\nThe following tables compares the features of the default pool with a private\npool:\n\nNetwork architecture\n--------------------\n\nPrivate pool is a fully-managed resource created by a user in a Google Cloud project.\nPrivate pools can be created, updated, and deleted via API, Google Cloud CLI,\nGoogle Cloud console, or managed via infrastructure provisioning tools such as\nTerraform.\n\nUsing Identity and Access Management permissions, builds run on private pools can be submitted\ncross project; that is builds don't have to originate from the same project as\nthe private pool. Likewise, the service account the build runs as can be\nconfigured to allow workers to access resources from other Google Cloud projects\nduring a build.\n\nPrivate pools are hosted in a Google-owned\n[service producer network](/vpc/docs/private-services-access) that comes\nwith internal IP addresses. For your builds to access resources in your private\nnetwork, you can create a private VPC peering connection between\nyour VPC network and the service producer network.\n\nThe following diagram shows how builds are routed to the private pool. In this\nsetup, the customer has two projects sending builds to Cloud Build.\nThe customer has configured all the builds from these projects to be routed to\ntheir private pool. The service producer network, where the private pool is in, is\npeered to the customer's VPC network giving the builds access to\nprivate resources in the customer's VPC network.\n\nWhat's next\n-----------\n\n- Learn how to [set up your environment to create private pools](/build/docs/private-pools/set-up-private-pool-environment).\n- Learn how to [create and manage private\n pools](/build/docs/private-pools/create-manage-private-pools).\n- Learn how to [configure commonly used networking use cases](/build/docs/private-pools/use-in-private-network).\n- Learn how to [use VPC Service Controls with private pools](/build/docs/private-pools/using-vpc-service-controls)."]]
