Disconnected environment

As explained in Google Anthos in Action

A disconnected environment is an environment whose application services cannot communicate with services in other environments.

A disconnected environment is an environment whose application services cannot communicate with services in other environments. Anthos supports this topology when environments remain isolated while retaining limited connectivity to GCP for control-plane traffic. section 10.1.2

Operational implications include:

• Each Anthos cluster must connect to GCP when registration is required, including for certain platform capabilities. section 10.1.2
• Multicluster ingress requires every participating cluster to be registered to GCP, even though application services across the disconnected environments cannot communicate. section 10.1.2
• Service-to-service connectivity across environments is unavailable by design, unlike TLS or mTLS gateway-based connectivity over shared networks. section 10.1.2

Figure 10.5 Dedicated Interconnect between GCP and an on-prem data center

Use the dedicated-interconnect diagram to contrast private connectivity to GCP with the application-level isolation of disconnected environments. section 10.1.2

How Google Anthos in Action covers it

How deep it goes

Defines service isolation and explains registration requirements, but does not provide configuration steps or recovery procedures.

Examples

Uses GCP-registered Anthos clusters and multicluster ingress as concrete deployment cases.

What you can do after

Evaluate whether an Anthos topology can preserve application isolation while meeting GCP registration requirements.

How it connects

Connects Anthos clusters with GCP, cluster registration, control-plane traffic, and multicluster ingress.

liveBookmanning.com

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

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.