Google Distributed Cloud Edge

As explained in Google Anthos in Action

Google Distributed Cloud Edge is a fully managed Google solution that delivers hardware, operating systems, and software for telco network functions and edge applications at customer locations.

Google Distributed Cloud Edge (GDCE) is a fully managed edge platform for telco virtualized and cloud-native network functions and edge applications. It combines Google-provided hardware, operating systems, and software in Google-managed racks at customer locations. section 8.3.1 section 8.4

GDCE decomposes the deployment into several managed and customer-facing responsibilities:

• Supports public cloud edge locations, telco-owned sites, and enterprise sites such as retail stores, factory floors, branch offices, and stadiums. section 8.3.1
• Provides compute, storage, servers, and top-of-rack network switches, while Google ships, remotely monitors, and manages the underlying gear. section 8.3.1
• Uses Anthos on bare metal to support containerized workloads and virtual machines, with fleet management for hardware and software assets. section 8.3.1 section 8.4
• Organizes Kubernetes worker servers into node pools, while hosting the control plane on Google Cloud in a single compute region. section 8.3.1
• Connects users to Google Cloud through VPN access to customer VPC applications and other Google Cloud services. section 8.3.1
• Accelerates high-performance, low-latency workloads with technologies such as SR-IOV and DPDK. section 8.3.1

Enterprise edge site

A retailer, factory, branch office, or stadium can host Google-managed GDCE racks locally, run containerized applications or virtual machines, and connect those workloads to services in its VPC through VPN. section 8.3.1

Figure 8.3 Google Distributed Cloud Edge high-level architecture

Use the high-level architecture to relate Google-managed racks, the edge Kubernetes environment, and Google Cloud connectivity. section 8.3.1

How Google Anthos in Action covers it

How deep it goes

Explains deployment locations, managed responsibilities, cluster structure, connectivity, and performance features without detailing operational procedures.

Examples

Uses Google, telco, and enterprise edge sites, including retail stores, factory floors, branch offices, and stadiums.

What it assumes

Assumes familiarity with cloud, Kubernetes, virtual machines, and networking while identifying the customer’s local administrative responsibilities.

What you can do after

Operate/configure edge workloads through standard Google API tools while Google manages the infrastructure remotely.

How it connects

Connects Anthos on bare metal with Kubernetes, virtual machines, containers, VPN, VPC, SR-IOV, DPDK, and fleet management.

liveBookmanning.com

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

Related concepts

• Anthos on bare metaluses · Anthos on bare metal is an Anthos deployment option that runs Kubernetes and Anthos components directly on physical servers or supported virtual machines without requiring a specific hypervisor.
• cloud-native network functionuses · A cloud-native network function (CNF) is a telecommunications network function designed to run as modular, containerized software on cloud-native infrastructure.
• virtual network functionuses · A virtual network function (VNF) is a telecommunications network function implemented as software running on virtualized computing infrastructure.

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.