El 15 de septiembre del 2026, todos los entornos de Cloud Composer 1 y Cloud Composer 2 versión 2.0.x alcanzarán el final de su ciclo de vida previsto y no podrás usarlos. Te recomendamos que planifiques la migración a Cloud Composer 3.
En esta sección se explica cómo organizar redes a gran escala para entornos de Cloud Composer.
Cuotas de VPC, subredes y reglas de reenvío
Los servicios de Cloud Composer y GKE usan el peering de VPC para establecer conexiones entre los componentes de los entornos de Cloud Composer (proyecto de cliente y proyecto de arrendatario), así como entre un clúster de GKE y un plano de control de GKE.
Si tu proyecto tiene una configuración de red a gran escala, como una con cientos de redes y muchas configuraciones de peering de VPC, cuando intentes crear nuevos entornos de Cloud Composer, las operaciones podrían fallar debido a errores de cuota de VPC, subred o reglas de reenvío.
Estos son los errores que pueden aparecer:
Se ha alcanzado el número máximo de emparejamientos de VPC por red de VPC.
La cuota predeterminada para el número de emparejamientos de VPC en una sola VPC es 25 (a menos que solicites un aumento de esta cuota).
Se ha alcanzado el número máximo de intervalos de IP de subred principales y secundarias.
La cuota de este parámetro es de 400.
Se ha alcanzado el número máximo de reglas de reenvío del grupo de emparejamiento para el balanceo de carga TCP/UDP interno.
La cuota de este parámetro es de 175.
Para obtener más información sobre las cuotas predeterminadas de las VPCs en Google Cloud, consulta Cuotas y límites.
Información sobre las redes a gran escala para entornos de Cloud Composer
Para superar los problemas relacionados con estos límites, puedes organizar tus entornos de Cloud Composer en varias redes de VPC conectadas a tu VPC principal o de backbone, tal como se describe en las secciones siguientes.
Esta solución se puede aplicar a escenarios con y sin VPC compartida.
Configuración de redes a gran escala en un escenario sin VPC compartida
Para crear una configuración de red a gran escala para Cloud Composer, sigue estos pasos:
Crea una red de VPC de backbone.
Esta red actúa como centro de las redes de VPC individuales que alojan entornos de Cloud Composer.
Crea redes de VPC dedicadas para entornos de Cloud Composer. Puedes combinar varios entornos de Cloud Composer en una red de VPC. Por ejemplo, puedes asignarles los nombres composer-vpc-1, composer-vpc-2, etc.
Configuración de redes a gran escala en un escenario de VPC compartida
Para solucionar el problema de los límites de emparejamiento de redes en las redes de VPC compartidas, organiza tus entornos de Cloud Composer en varios proyectos y redes de VPC conectados a una VPC troncal.
Para crear una configuración de red de VPC compartida a gran escala para Cloud Composer, sigue estos pasos:
En el proyecto host, crea una red de VPC troncal.
Esta red conecta redes de VPC individuales para proyectos de servicio que ejecutan entornos de Cloud Composer.
En el proyecto host, crea redes de VPC para los entornos de Cloud Composer. Por ejemplo, puedes llamar a estas redes composer-shared-vpc-1, composer-shared-vpc-2, etc.
[[["Es fácil de entender","easyToUnderstand","thumb-up"],["Me ofreció una solución al problema","solvedMyProblem","thumb-up"],["Otro","otherUp","thumb-up"]],[["Es difícil de entender","hardToUnderstand","thumb-down"],["La información o el código de muestra no son correctos","incorrectInformationOrSampleCode","thumb-down"],["Me faltan las muestras o la información que necesito","missingTheInformationSamplesINeed","thumb-down"],["Problema de traducción","translationIssue","thumb-down"],["Otro","otherDown","thumb-down"]],["Última actualización: 2025-08-29 (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,["# Configure large-scale networks for Cloud Composer environments\n\n\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-------------------------------------------\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----------------------------------------------------------\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------------------------------------------------------\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--------------------------------------------------\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\n- [Configure Shared VPC](/composer/docs/composer-1/configure-shared-vpc)\n- [Create an environment](/composer/docs/composer-1/create-environments)"]]
