[[["이해하기 쉬움","easyToUnderstand","thumb-up"],["문제가 해결됨","solvedMyProblem","thumb-up"],["기타","otherUp","thumb-up"]],[["이해하기 어려움","hardToUnderstand","thumb-down"],["잘못된 정보 또는 샘플 코드","incorrectInformationOrSampleCode","thumb-down"],["필요한 정보/샘플이 없음","missingTheInformationSamplesINeed","thumb-down"],["번역 문제","translationIssue","thumb-down"],["기타","otherDown","thumb-down"]],["최종 업데이트: 2025-03-10(UTC)"],[[["This page outlines how to manage large-scale networks for Cloud Composer environments, addressing potential quota issues with VPC peerings, subnets, and forwarding rules."],["When 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."],["To 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."],["In 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."],["For 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."]]],[]]
