Pada 15 September 2026, semua lingkungan Cloud Composer 1 dan Cloud Composer 2 versi 2.0.x akan mencapai akhir masa pakainya yang direncanakan, dan Anda tidak akan dapat menggunakannya. Sebaiknya rencanakan migrasi ke Cloud Composer 3.
Bagian ini menjelaskan cara mengatur jaringan skala besar untuk
lingkungan Cloud Composer.
Kuota untuk VPC, subnet, dan aturan penerusan
Layanan Cloud Composer dan GKE menggunakan peering VPC untuk
membangun koneksi antara
komponen lingkungan Cloud Composer
(Project Pelanggan dan Project Tenant) serta antara cluster GKE
dan Bidang Kontrol GKE.
Jika project Anda memiliki konfigurasi jaringan skala besar, seperti yang memiliki
ratusan jaringan dan banyak peering VPC yang dikonfigurasi, saat Anda mencoba
membuat lingkungan Cloud Composer baru, operasi mungkin gagal
karena error kuota aturan VPC, subnet, atau penerusan.
Error yang mungkin Anda temui adalah:
Jumlah maksimum peering VPC per jaringan VPC tunggal telah tercapai.
Kuota default untuk sejumlah peering VPC dalam satu VPC adalah 25
(kecuali jika Anda meminta peningkatan kuota ini).
Jumlah maksimum rentang IP subnet primer dan sekunder tercapai.
Kuota untuk parameter ini adalah 400.
Jumlah maksimum aturan penerusan dalam grup peering untuk Load Balancing TCP/UDP internal telah tercapai.
Kuota untuk parameter ini adalah 175.
Untuk mengetahui informasi selengkapnya tentang kuota default untuk VPC di Google Cloud, lihat
Kuota dan batas.
Tentang jaringan berskala besar untuk lingkungan Cloud Composer
Untuk mengatasi tantangan terkait batas ini, Anda dapat mengatur
lingkungan Cloud Composer ke dalam beberapa jaringan VPC yang terhubung ke
VPC utama/backbone seperti yang dijelaskan di bagian berikut.
Solusi ini berlaku untuk skenario VPC Bersama dan non-VPC Bersama.
Penyiapan jaringan skala besar dalam skenario non-VPC Bersama
Untuk membuat penyiapan jaringan berskala besar untuk Cloud Composer:
Buat jaringan VPC backbone.
Jaringan ini berfungsi sebagai hub untuk setiap jaringan VPC yang menghosting
lingkungan Cloud Composer.
Buat jaringan VPC khusus untuk
lingkungan Cloud Composer. Anda dapat menggabungkan beberapa
lingkungan Cloud Composer menjadi satu jaringan VPC. Misalnya,
Anda dapat memberi nama jaringan ini composer-vpc-1, composer-vpc-2, dan sebagainya.
Penyiapan jaringan skala besar dalam skenario VPC Bersama
Untuk mengatasi masalah batas peering jaringan di jaringan VPC Bersama, atur
lingkungan Cloud Composer Anda ke dalam beberapa project dan jaringan
VPC yang terhubung ke satu VPC backbone.
Untuk membuat penyiapan jaringan VPC Bersama skala besar untuk Cloud Composer:
Di project host,
buat jaringan VPC backbone.
Jaringan ini menghubungkan setiap jaringan VPC untuk project layanan yang menjalankan
lingkungan Cloud Composer.
Di project host,
buat jaringan VPC
untuk lingkungan Cloud Composer. Misalnya, Anda dapat memberi nama jaringan
ini composer-shared-vpc-1, composer-shared-vpc-2, dan sebagainya.
[[["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-26 UTC."],[[["\u003cp\u003eThis page outlines how to manage large-scale networks for Cloud Composer environments, addressing potential quota issues with VPC peerings, subnets, and forwarding rules.\u003c/p\u003e\n"],["\u003cp\u003eWhen dealing with many networks and VPC peerings, new Cloud Composer environments may fail due to reaching the maximum number of VPC peerings, subnet IP ranges, or forwarding rules, with default quotas being 25, 400, and 175, respectively.\u003c/p\u003e\n"],["\u003cp\u003eTo manage these limitations, you can organize Cloud Composer environments into multiple VPC networks connected to a central "backbone" VPC, which is applicable to both Shared and non-Shared VPC scenarios.\u003c/p\u003e\n"],["\u003cp\u003eIn a non-Shared VPC setup, you should create a backbone VPC network, create dedicated VPC networks for Cloud Composer environments, and establish connectivity between these networks and the backbone using HA VPN tunnels.\u003c/p\u003e\n"],["\u003cp\u003eFor Shared VPC setups, organize Cloud Composer environments into multiple projects and VPC networks, establish connectivity between these networks and a backbone VPC in the host project, and then configure Cloud Composer environments within the Shared VPC setup.\u003c/p\u003e\n"]]],[],null,["\u003cbr /\u003e\n\n\u003cbr /\u003e\n\n\nCloud Composer 3 \\| [Cloud Composer 2](/composer/docs/composer-2/configure-large-scale-networks \"View this page for Cloud Composer 2\") \\| **Cloud Composer 1**\n\n\u003cbr /\u003e\n\n\u003cbr /\u003e\n\n\u003cbr /\u003e\n\n\u003cbr /\u003e\n\n\u003cbr /\u003e\n\n\u003cbr /\u003e\n\nThis section explains how to organize large-scale networks for\nCloud Composer environments.\n\nQuotas for VPC, subnet and forwarding rules\n\nCloud Composer and GKE services use VPC peerings to\nestablish connections between the\n[components of Cloud Composer environments](/composer/docs/composer-1/environment-architecture)\n(Customer Project and Tenant Project) and between a GKE\ncluster and a GKE Control Plane.\n\nIf your project has a large-scale network configuration, such as one with\nhundreds of networks and many VPC peerings configured, then when you try to\ncreate new Cloud Composer environments, the operations might fail\nbecause of VPC, subnet or forwarding rules quota errors.\n\nThe errors that you might encounter are:\n\n- The maximum number of VPC peerings per single VPC network is reached.\n\n The default quota for a number of VPC peerings within a single VPC is 25\n (unless you request an increase of this quota).\n- The maximum number of primary and secondary subnet IP ranges is reached.\n\n The quota for this parameter is 400.\n- The maximum number of forwarding rules in the peering group for Internal TCP/\n UDP Load Balancing is reached.\n\n The quota for this parameter is 175.\n\nFor more information about default quotas for VPCs in Google Cloud, see\n[Quotas and limits](/vpc/docs/quota#vpc-peering).\n\nAbout large-scale networks for Cloud Composer environments\n\nTo overcome challenges related to these limits, you can organize your\nCloud Composer environments into several VPC networks connected to\nyour main/backbone VPC as it is described in the following sections.\n\nThis solution is applicable to Shared VPC and non-Shared VPC scenarios.\n\nLarge-scale network setup in a non-Shared VPC scenario\n\nTo create a large-scale network setup for Cloud Composer:\n\n1. [Create a backbone VPC network](/vpc/docs/create-modify-vpc-networks#create-custom-network).\n This network acts as a hub for individual VPC networks that host\n Cloud Composer environments.\n\n2. [Create dedicated VPC networks](/vpc/docs/create-modify-vpc-networks#create-custom-network) for\n Cloud Composer environments. You can combine several\n Cloud Composer environments into one VPC network. For example,\n you can name these networks `composer-vpc-1`, `composer-vpc-2`, and so on.\n\n3. Establish connectivity between Cloud Composer environment VPC\n networks and the backbone VPC by\n [creating HA VPN tunnels](/network-connectivity/docs/vpn/how-to).\n\n| **Note:** The recommended way of configuring VPC network is to use custom mode when creating subnets.\n\nLarge-scale network setup in a Shared VPC scenario\n\nTo solve the network peering limits issue in a Shared VPC networks, organize\nyour Cloud Composer environments into several projects and VPC\nnetworks connected to one backbone VPC.\n\nTo create a large-scale Shared VPC network setup for Cloud Composer:\n\n1. In the host project,\n [create a backbone VPC network](/vpc/docs/create-modify-vpc-networks#create-custom-network).\n This network connects individual VPC networks for service projects running\n Cloud Composer environments.\n\n2. In the host project,\n [create VPC networks](/vpc/docs/create-modify-vpc-networks#create-custom-network)\n for Cloud Composer environments. For example, you can name these\n networks `composer-shared-vpc-1`, `composer-shared-vpc-2`, and so on.\n\n3. Establish connectivity between these VPC networks and the backbone VPC\n network by manually\n [creating HA VPN tunnels](/network-connectivity/docs/vpn/how-to).\n\n4. Configure Cloud Composer environments\n [in the Shared VPC setup](/composer/docs/composer-1/configure-shared-vpc).\n\n| **Note:** The recommended way of configuring VPC network is to use custom mode when creating subnets.\n\nWhat's next\n\n- [Configure Shared VPC](/composer/docs/composer-1/configure-shared-vpc)\n- [Create an environment](/composer/docs/composer-1/create-environments)"]]
