Tetap teratur dengan koleksi
Simpan dan kategorikan konten berdasarkan preferensi Anda.
Halaman ini memberikan ringkasan tentang kumpulan pribadi dan menjelaskan fitur-fiturnya.
Jika Anda baru menggunakan Cloud Build, baca Ringkasan Cloud Build.
Ringkasan kumpulan default dan kumpulan pribadi
Secara default, saat Anda menjalankan build di Cloud Build, build akan berjalan di
lingkungan terhosting dan aman dengan akses ke internet publik. Setiap build berjalan di
pekerja-nya sendiri dan terisolasi dari beban kerja lainnya. Anda dapat menyesuaikan
build dengan beberapa cara, termasuk meningkatkan ukuran jenis mesin atau
mengalokasikan lebih banyak ruang disk. Kumpulan default memiliki batasan terkait seberapa banyak Anda dapat menyesuaikan lingkungan, terutama terkait akses jaringan pribadi.
Kumpulan pribadi adalah kumpulan pekerja khusus dan pribadi yang menawarkan penyesuaian
yang lebih besar pada lingkungan build, termasuk kemampuan untuk mengakses resource
di jaringan pribadi. Kumpulan pribadi, mirip dengan kumpulan default, dihosting dan dikelola sepenuhnya oleh Cloud Build serta diskalakan ke atas dan ke bawah hingga nol, tanpa infrastruktur untuk disiapkan, diupgrade, atau diskalakan. Karena kumpulan pribadi adalah
resource khusus pelanggan, Anda dapat mengonfigurasinya dengan lebih banyak cara.
Tabel berikut membandingkan fitur kumpulan default dengan kumpulan
pribadi:
Build berjalan di region tempat Anda membuat kumpulan pribadi.
Arsitektur jaringan
Kumpulan pribadi adalah resource terkelola sepenuhnya yang dibuat oleh pengguna dalam Google Cloud project.
Pool pribadi dapat dibuat, diperbarui, dan dihapus melalui API, Google Cloud CLI, konsolGoogle Cloud , atau dikelola melalui alat penyediaan infrastruktur seperti Terraform.
Dengan menggunakan izin Identity and Access Management, build yang berjalan di kumpulan pribadi dapat dikirimkan
lintas project; artinya build tidak harus berasal dari project yang sama dengan
kumpulan pribadi. Demikian pula, akun layanan yang dijalankan build dapat
dikonfigurasi untuk memungkinkan pekerja mengakses resource dari project Google Cloud lain
selama build.
Kumpulan pribadi dihosting di
jaringan produsen layanan milik Google yang dilengkapi dengan alamat IP internal. Agar build dapat mengakses resource di jaringan
pribadi, Anda dapat membuat koneksi peering VPC pribadi antara jaringan VPC dan jaringan produsen layanan.
Diagram berikut menunjukkan cara build dirutekan ke kumpulan pribadi. Dalam
penyiapan ini, pelanggan memiliki dua project yang mengirim build ke Cloud Build.
Pelanggan telah mengonfigurasi semua build dari project ini untuk dirutekan ke kumpulan pribadinya. Jaringan produsen layanan, tempat kumpulan pribadi berada, dihubungkan ke jaringan VPC pelanggan yang memberi build akses ke
resource pribadi di jaringan VPC pelanggan.
[[["Mudah dipahami","easyToUnderstand","thumb-up"],["Memecahkan masalah saya","solvedMyProblem","thumb-up"],["Lainnya","otherUp","thumb-up"]],[["Sulit dipahami","hardToUnderstand","thumb-down"],["Informasi atau kode contoh salah","incorrectInformationOrSampleCode","thumb-down"],["Informasi/contoh yang saya butuhkan tidak ada","missingTheInformationSamplesINeed","thumb-down"],["Masalah terjemahan","translationIssue","thumb-down"],["Lainnya","otherDown","thumb-down"]],["Terakhir diperbarui pada 2025-08-25 UTC."],[[["\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)."]]
