An enterprise is planning a multi-region Google Cloud deployment that connects to an on-premises data center using Cloud Interconnect. The environment must host Google Kubernetes Engine (GKE) clusters using alias IPs and prevent IP address collisions. Sequence the following steps in the correct order to properly plan and implement the Virtual Private Cloud (VPC) network architecture from initial network assessment to hybrid connectivity configuration.
- 1Audit existing on-premises IP space () and catalog reserved address blocks to identify available, contiguous IPv4 ranges for GCP allocation.
- 2Create a custom-mode VPC network in the Google Cloud project to prevent automatic allocation of default regional subnets.
- 3Provision custom subnets in target regions with non-overlapping primary IPv4 CIDR blocks selected from the unallocated address space.
- 4Configure secondary IPv4 CIDR ranges on the regional subnets specifically designated for GKE Pods and Services.
- 5Configure Cloud Router BGP sessions over Cloud Interconnect to advertise the newly provisioned VPC primary and secondary subnet ranges to the on-premises network.
Cevap
The correct sequence begins with auditing existing on-premises IP space, followed by creating a custom-mode VPC network, provisioning custom subnets with non-overlapping primary CIDR ranges, configuring secondary CIDR ranges for GKE alias IPs, and finally setting up Cloud Router BGP advertising to the on-premises network.
Proper VPC network planning for enterprise hybrid environments follows a logical sequence: identifying unallocated IP ranges on-premises first, creating a custom-mode VPC network to maintain full subnet control, establishing regional subnets with primary CIDRs, provisioning secondary ranges for GKE cluster alias IPs, and finally advertising the completed CIDRs across BGP over Cloud Interconnect.
Adım Adım Çözüm
Anahtar Kavram
Planning Enterprise Hybrid VPC Networks and Subnets
Tahmini Süre:2m 0s