A cloud engineering team needs to expand the primary IP range of a subnet within an auto-mode Virtual Private Cloud (VPC) network in Google Cloud to accommodate new Compute Engine instances without disrupting existing network traffic. Place the steps required to safely convert the network mode and expand the subnet IP range into the correct sequential order.
- 1Audit existing network routes and verify that the target expanded CIDR range will not overlap with on-premises or peered networks.
- 2Execute `gcloud compute networks update [VPC_NAME] --switch-to-custom-mode` to convert the VPC network from auto mode to custom mode.
- 3Execute `gcloud compute networks subnets expand-ip-range [SUBNET_NAME] --prefix-length [NEW_PREFIX]` to expand the primary IP range.
- 4Verify the expanded subnet configuration using `gcloud compute networks subnets describe` and launch new instances into the expanded address space.
Cevap
The correct order begins with verifying that the target expanded CIDR range will not cause IP address overlap, followed by switching the VPC network from auto mode to custom mode using the gcloud compute networks update command. Next, expand the primary subnet range using gcloud compute networks subnets expand-ip-range, and finally verify the updated configuration and deploy workloads into the expanded subnet space.
Expanding a subnet primary IP range in Google Cloud requires IP planning first to avoid collisions, followed by converting an auto-mode VPC to custom mode, executing the gcloud expand-ip-range command, and finally verifying the change before deploying workloads.
Adım Adım Çözüm
Anahtar Kavram
Auto-mode to custom-mode VPC conversion and primary IPv4 subnet expansion