liveBook · Manning

Network host project

As explained in Google Anthos in Action

A network host project is the Google Cloud project that owns and centrally administers a shared VPC network and makes it available to attached service projects.

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

Figure 10.3 Shared VPC architecture in GCP
10-03

Use the shared-VPC architecture to compare centralized network ownership with service-project resource placement. section 10.1.1

Figure 10.14 Anthos GKE multicluster networking
10-14

Use the multicluster networking diagram to trace shared-VPC connectivity across Anthos GKE clusters and regions. section 10.3.1

How Google Anthos in Action covers it

How deep it goes
Explains ownership, shared resources, project boundaries, and regional multicluster deployment architecture.
Examples
Uses platform_admins and product service projects, regional redundancy, zonal clusters, shared subnets, and tenant namespaces.
What you can do after
Configure a Shared VPC topology that separates network administration from Anthos, product, and tenant workloads.
How it connects
Connects Shared VPC, service projects, IAM, Anthos, GKE, VPC-native clusters, and multicluster service mesh.

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Google Anthos in Action. The section links point to the parts of the book it draws on.