GCP VPC Subnet Planner
Google Cloud VPC subnet planning reflecting GCP 4 reserved addresses and secondary alias IP ranges for GKE.
Google Cloud VPC Subnetting & Alias IP Architecture
Google Cloud uses a fundamentally different networking model than AWS or Azure. In GCP, VPCs are global resources, while subnets are regional rather than zonal. Furthermore, GCP reserves exactly 4 IP addresses per subnet (not 5 like its cloud counterparts).
Regional Subnet Span
A single subnet covers all zones within a region (such as Sydney or Melbourne), simplifying routing tables and cross-zone high availability.
Secondary Ranges for GKE
Seamlessly model dedicated alias IP ranges for Kubernetes Pods and Services required by VPC-native GKE clusters.
Exact 4-IP Deduction
Accounts for .0 (network), .1 (default gateway), .254 (Google future use), and .255 (broadcast) for 100% sizing accuracy.
Related Cloud Planners
Frequently Asked Questions
Why does Google Cloud reserve 4 IP addresses per subnet instead of 5?
Google Cloud VPC subnets reserve exactly 4 IP addresses: (1) .0 network address; (2) .1 default gateway; (3) second-to-last address (.254 on /24) reserved for future use; (4) last address (.255 on /24) broadcast address.
Are subnets in Google Cloud VPC regional or zonal?
Google Cloud VPC subnets are regional resources. A single subnet automatically spans all Availability Zones within that region. Compute Engine instances and GKE nodes across different zones can be attached to the same subnet.
What are secondary IP ranges in Google Cloud?
Secondary IP ranges (alias IP ranges) are additional CIDR blocks attached to a primary subnet, commonly used by Google Kubernetes Engine (GKE) to assign distinct routable IP address pools to Pods and Services without creating separate virtual networks.
Need this designed for a real production environment?
Consult with Gurinder Singh and vetted cloud specialists for Azure Landing Zones, AWS VPC peering, and hybrid connectivity.