A network host project centrally owns and administers a shared VPC, including its subnets, firewall rules, and network permissions. Attached service projects use those shared resources while retaining project-level separation for products, tenants, and platform administration. section 10.1.1
A shared-VPC host project establishes these operational boundaries:
- A centralized networking team controls the host project and enforces organizational networking practices. section 10.1.1
- Service projects consume host-project subnets while isolating IAM permissions by product, tenant, or platform function. section 10.1.1
- A platform_admins service project can contain the Anthos GKE clusters, while product and environment projects provide separate tenant landing zones. section 10.1.1
Regional Anthos platform
A production deployment can use project-0-nethost-prod for the shared VPC, project-1-platform_admins-prod for Anthos clusters, and project-2-product1-prod for product resources. Two regions provide regional redundancy; multiple zonal clusters per region add cluster- and zone-level resiliency. section 10.3.1
Use the shared-VPC architecture to compare centralized network ownership with service-project resource placement. section 10.1.1
Use the multicluster networking diagram to trace shared-VPC connectivity across Anthos GKE clusters and regions. section 10.3.1
