liveBook · Manning

Multi-cluster setup

As explained in Google Anthos in Action

A multicluster setup is an architecture that distributes workloads or environments across multiple Kubernetes clusters.

A multi-cluster setup distributes application workloads across multiple Anthos GKE clusters, supporting high availability, global latency requirements, and safer infrastructure lifecycle changes. section 12.6

Use a single cluster with multiple namespaces for single-site or nonproduction environments; use multiple clusters when availability, geographic reach, or staged release isolation matters. section 12.6

A representative deployment combines:

  • Anthos GKE clusters hosting a microservices voting application. section 12.6
  • Separate namespaces for Voting, Transfer, and Results services. section 12.6
  • Cloud Memorystore, Cloud SQL, and Secret Manager for state and credentials. section 12.6
  • A CI/CD pipeline that rolls changes out to individual clusters before full release. section 12.6

How Google Anthos in Action covers it

How deep it goes
Explains deployment selection and rollout purpose, but stops short of cluster orchestration procedures or configuration details.
Examples
Uses a voting system with Voting, Transfer, and Results namespaces plus Redis, Postgres, and secret-management services.
What it assumes
Assumes Kubernetes, microservices, namespaces, managed services, and CI/CD familiarity rather than teaching them from zero.
What you can do after
Operate staged application releases across individual Anthos clusters before completing a broader deployment.
How it connects
Connects Kubernetes, Anthos GKE, namespaces, microservices, CI/CD, managed services, and Terraform.
Cover of Google Anthos in Action
liveBookmanning.com
Read Google Anthos in Action on liveBook Get the book at manning.com

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.