Stay organized with collections Save and categorize content based on your preferences.
This page provides an overview of connected deployments of Google Distributed Cloud (formerly Google Distributed Cloud Edge), including information about when to use it and its limitations and known issues.
A connected deployment of Distributed Cloud lets you run Google Kubernetes Engine (GKE) clusters on dedicated hardware provided and maintained by either Google or a Google-certified Systems Integrator (SI) that is installed directly on your premises and connects to your local network.
Deploying workloads on a connected Distributed Cloud installation functions in a similar way to deploying workloads on cloud-based GKE clusters. After the hardware has been deployed, your cluster administrator provisions Distributed Cloud connected clusters by using the Google Cloud console or the Google Cloud CLI. In addition, your network administrator configures the Distributed Cloud networking components so that your workloads can communicate with your local network and each other. Your application owners can then deploy workloads to those clusters.
Connected deployments of Distributed Cloud support running workloads in Kubernetes containers and, on select hardware configurations, in virtual machines. Select hardware configurations also support GPU-based workloads.
Connected deployments of Distributed Cloud are available in one of the following form factors:
Distributed Cloud connected rack. Deployed as a pair of base racks, also called a base rack set, and optionally up to three expansion racks. Each rack holds three to twelve Distributed Cloud connected machines, two top-of-rack (ToR) switches, and all necessary networking and electrical hardware. A base rack set also holds two aggregator switches that allow you to connect expansion racks with redundancy. This form factor is a preview-level offering.
Distributed Cloud connected server. A standalone Distributed Cloud connected server that connects directly to your local network through your own network hardware.
For more information on each form factor, see Distributed Cloud form factors.
Google remotely monitors and maintains your connected deployments of Distributed Cloud, which includes installing software updates and security patches, resolving configuration issues, and diagnosing the Distributed Cloud hardware. To resolve an issue that can't be resolved remotely, you must provide Google's or the Google-certified SI's authorized personnel physical access to the Distributed Cloud hardware.
Your Distributed Cloud connected deployment uses a secure Cloud VPN connection to access Google Cloud services and your applications that run within Google Cloud and your Virtual Private Cloud (VPC) network.
For a technical overview of connected deployments Distributed Cloud, see How Distributed Cloud connected works.
When to use Distributed Cloud connectedA connected deployment of Distributed Cloud is specifically designed to address the following scenarios in which conventional Google Cloud deployments might not be sufficient:
A Distributed Cloud connected zone has the following limitations compared to a conventional cloud-based GKE zone:
Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License, and code samples are licensed under the Apache 2.0 License. For details, see the Google Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.
Last updated 2025-08-07 UTC.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-07 UTC."],[[["Google Distributed Cloud connected allows running Google Kubernetes Engine (GKE) clusters on dedicated, on-premises hardware managed by Google or a certified System Integrator, connecting directly to your local network."],["Workloads are deployed to Distributed Cloud connected clusters similarly to cloud-based GKE, but hardware and networking are configured on-premises by cluster and network administrators."],["This service is offered in two form factors: Distributed Cloud connected rack (preview), a set of base and expansion racks, and Distributed Cloud connected server, a standalone server directly connected to your network."],["It is designed for scenarios requiring stable, low-latency network connections, on-premises data storage, or high-volume local data processing that cannot rely on standard internet connection."],["Compared to cloud-based solutions, it has limited processing capacity and certain workload restrictions, which should be taken into account during planning."]]],[]]
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4