Cloud landing zone

As explained in Google Anthos in Action

A cloud landing zone is a foundational cloud environment configured with standardized identity, networking, security, governance, and billing controls.

A cloud landing zone is the resource boundary prepared for a service on Anthos. It typically combines one or more Kubernetes namespaces with policies, while non-Anthos resources remain in the service’s own cloud project. section 10.1.1

A landing zone establishes:

• Identity, network configuration, security, and billing controls required before migration or deployment. section 15.3.1
• A tenancy boundary in which each product or tenant deploys only to its assigned namespaces and follows its policies. section 10.3.1
• A network arrangement that can use a shared VPC, separate VPCs, or multiple clusters and regions according to connectivity and resiliency needs. section 10.1.1 section 10.3.1

Migration setup

Before migrating workloads, create the processing environment, define migration sources, and configure the landing zone. Cloud Foundation Toolkit or Terraform can make the foundation repeatable. Discovery tools then identify workloads for migration, after which generated images, Dockerfiles, volumes, and deployment YAML can be tested on GKE or Anthos. section 15.3.1

Figure 10.3 Shared VPC architecture in GCP

Use the shared VPC architecture to inspect how network resources can remain in a host project while subnets serve multiple service projects. section 10.1.1

How Google Anthos in Action covers it

How deep it goes

Defines boundaries, policies, projects, and network choices, then connects them to migration setup without detailing individual identity or billing implementations.

Examples

Uses Anthos tenant namespaces, shared and multiple VPCs, multicluster services, Terraform, Cloud Foundation Toolkit, and migration discovery tools.

What you can do after

Build it from scratch as a repeatable foundation for Anthos deployment or migration using projects, policies, networks, and automation templates.

How it connects

Connects Kubernetes namespaces, multitenancy, service projects, shared VPCs, multicluster networking, service meshes, and infrastructure as code.

liveBookmanning.com

Read Google Anthos in Action on liveBook Get the book at manning.com

Related concepts

• namespaceuses · A namespace is a naming context or identifier space in which names are defined and resolved, distinguishing them from names in other contexts.
• data warehousehas part · A data warehouse is a centralized repository of integrated data organized and optimized for analytical querying, reporting, and analysis.

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.