A 15 de setembro de 2026, todos os ambientes do Cloud Composer 1 e do Cloud Composer 2 versão 2.0.x vão atingir o fim da vida útil planeado e não vai poder usá-los. Recomendamos que planeie a migração para o Cloud Composer 3.
Quotas para regras de VPC, sub-rede e encaminhamento
Os serviços Cloud Composer e GKE usam interligações de VPCs para
estabelecer ligações entre os
componentes dos ambientes do Cloud Composer
(projeto do cliente e projeto do inquilino) e entre um cluster do GKE
e um plano de controlo do GKE.
Se o seu projeto tiver uma configuração de rede de grande escala, como uma com centenas de redes e muitas interligações de VPC configuradas, quando tentar criar novos ambientes do Cloud Composer, as operações podem falhar devido a erros de quota de VPC, sub-rede ou regras de encaminhamento.
Os erros que pode encontrar são:
O número máximo de intercâmbios da VPC por rede da VPC foi atingido.
A quota predefinida para um número de interligações de VPC numa única VPC é de 25 (a menos que peça um aumento desta quota).
Foi atingido o número máximo de intervalos de IPs de sub-rede primários e secundários.
A quota para este parâmetro é de 400.
O número máximo de regras de encaminhamento no grupo de peering para o balanceamento de carga de TCP/UDP interno foi atingido.
A quota para este parâmetro é 175.
Para mais informações sobre as quotas predefinidas para VPCs no Google Cloud, consulte o artigo
Quotas e limites.
Acerca das redes de grande escala para ambientes do Cloud Composer
Para superar os desafios relacionados com estes limites, pode organizar os seus ambientes do Cloud Composer em várias redes VPC ligadas à sua VPC principal/de base, conforme descrito nas secções seguintes.
Esta solução é aplicável a cenários de VPC partilhada e não partilhada.
Configuração de rede em grande escala num cenário de VPC não partilhada
Para criar uma configuração de rede em grande escala para o Cloud Composer:
Crie uma rede de VPC de backbone.
Esta rede funciona como um hub para redes VPC individuais que alojam ambientes do Cloud Composer.
Crie redes VPC dedicadas para os ambientes do Cloud Composer. Pode combinar vários ambientes do Cloud Composer numa rede VPC. Por exemplo, pode dar os nomes composer-vpc-1, composer-vpc-2, etc., a estas redes.
Configuração de rede em grande escala num cenário de VPC partilhada
Para resolver o problema dos limites de intercâmbio de redes numa rede VPC partilhada, organize os seus ambientes do Cloud Composer em vários projetos e redes VPC ligados a uma VPC principal.
Para criar uma configuração de rede VPC partilhada em grande escala para o Cloud Composer:
No projeto anfitrião,
crie uma rede VPC principal.
Esta rede liga redes VPC individuais para projetos de serviços que executam ambientes do Cloud Composer.
No projeto anfitrião,
crie redes VPC
para ambientes do Cloud Composer. Por exemplo, pode dar os nomes composer-shared-vpc-1, composer-shared-vpc-2, etc., a estas redes.
[[["Fácil de entender","easyToUnderstand","thumb-up"],["Meu problema foi resolvido","solvedMyProblem","thumb-up"],["Outro","otherUp","thumb-up"]],[["Difícil de entender","hardToUnderstand","thumb-down"],["Informações incorretas ou exemplo de código","incorrectInformationOrSampleCode","thumb-down"],["Não contém as informações/amostras de que eu preciso","missingTheInformationSamplesINeed","thumb-down"],["Problema na tradução","translationIssue","thumb-down"],["Outro","otherDown","thumb-down"]],["Última atualização 2025-08-29 UTC."],[[["\u003cp\u003eThis document provides guidance on organizing large-scale networks for Cloud Composer environments, specifically addressing limitations related to VPC peering quotas.\u003c/p\u003e\n"],["\u003cp\u003ePrivate Service Connect (PSC) is recommended over VPC peering for Cloud Composer 2 environments, as it avoids VPC peering quotas.\u003c/p\u003e\n"],["\u003cp\u003eFor large-scale networks, Cloud Composer environments should be organized into several VPC networks connected to a central backbone VPC network to manage VPC peering, subnet, and forwarding rule quotas.\u003c/p\u003e\n"],["\u003cp\u003eBoth non-Shared VPC and Shared VPC scenarios are addressed, with specific steps for setting up large-scale networks using a backbone VPC and dedicated VPC networks for Cloud Composer environments.\u003c/p\u003e\n"],["\u003cp\u003eHA VPN tunnels are recommended to establish connectivity between Cloud Composer environment VPC networks and the backbone network, ensuring there is no direct peering that could result in overreach on quotas.\u003c/p\u003e\n"]]],[],null,["\u003cbr /\u003e\n\n\u003cbr /\u003e\n\n\nCloud Composer 3 \\| **Cloud Composer 2** \\| [Cloud Composer 1](/composer/docs/composer-1/configure-large-scale-networks \"View this page for 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\nUse Private Service Connect instead of VPC peering networking **Important:** This guide applies only to environments that use VPC peerings. PSC is the default connectivity type for environments in Cloud Composer 2 (when you create an environment in Google Cloud console), and it does not use VPC peering quotas (your environment's cluster still [uses VPC quotas](/composer/docs/composer-2/configure-private-ip#requirements)).\n\nFor more information, see\n[Configure Private Service Connect](/composer/docs/composer-2/configure-private-service-connect).\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-2/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-2/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-2/configure-shared-vpc)\n- [Create an environment](/composer/docs/composer-2/create-environments)"]]
