Google Distributed Cloud 解決方案可將基礎架構和服務延伸至資料中心。 Google Cloud我們提供 Google Distributed Cloud 的連結和無網路連線設定，這些設定會在 Google 提供的硬體上執行。我們也提供 Google Distributed Cloud，這項產品僅含軟體，可在您自己的硬體上執行。Google Distributed Cloud 軟體可安裝在 VMware 或裸機上。本指南適用於在 VMware vSphere 環境中，透過自有硬體執行的 Google Distributed Cloud 軟體。
Google Distributed Cloud 以 Google Kubernetes Engine (GKE) 為基礎，並提供專屬的 Kubernetes 套件，可擴充 GKE，供內部部署環境使用。有了 Google Distributed Cloud，您可以在自有環境中建立、管理及升級 GKE 叢集，同時使用Google Cloud 功能，並在叢集上大規模部署及操作容器化應用程式，充分運用 Google 的基礎架構。
Google Distributed Cloud 會擴大 GKE 的使用範圍，讓您在自己的地端部署 vSphere 環境，並在 Google Cloud 中管理這些叢集、一般 GKE 叢集和其他環境中的叢集，只要向機群註冊即可。
Google Distributed Cloud 軟體是在資料中心而非Google Cloud中執行，因此除了 GKE 軟體本身，您也必須安裝一些管理與控制層軟體。在資料中心運作的軟體會於安裝和升級時下載。
下圖顯示安裝完成後的簡化結果。
Google Distributed Cloud 架構，含一個使用者叢集
重要元件
在 VMware 上安裝 Google Distributed Cloud 時，僅需下列軟體元件：
使用者叢集會執行實作應用程式的工作負載，就像在 GKE on Google Cloud中一樣。執行工作負載的節點稱為「工作站節點」。使用者叢集也有一或多個控制層節點。在上圖中，使用者叢集有一個控制層節點。
管理員叢集會管理一或多個使用者叢集。在上圖中，管理員叢集有三個控制層節點。
管理工作站是獨立的機器，內含叢集建立者和開發人員管理安裝作業所需的工具：
從管理員工作站執行 gkectl，即可建立及更新叢集，並執行其他管理工作
從管理員工作站執行 kubectl，即可與管理員和使用者叢集互動，包括部署及管理工作負載
Google Cloud 控制台提供專案的網頁介面，包括 VMware 上的叢集。 Google Cloud 您可以透過 Google Cloud 控制台執行部分管理工作，包括建立叢集，不必在管理員工作站上執行指令。
叢集管理員和開發人員會使用 kubectl 和虛擬 IP 位址 (VIP)，存取管理員和使用者叢集中的控制層。您可以在建立叢集時設定 VIP。使用者和開發人員在使用者叢集中呼叫工作負載時，會使用 Service 和 Ingress 虛擬 IP 位址。安裝中的每個節點也都有自己的 IP 位址。如要進一步瞭解 Google Distributed Cloud 的 IP 規劃，請參閱「規劃 IP 位址」。
連線至車隊
所有 Google Distributed Cloud 叢集都是機群的成員：Kubernetes 叢集的邏輯分組。貴機構可透過機群，將管理單位從個別叢集提升為整個叢集群組，並協助團隊採用與 Google 類似的最佳做法。您可以在 Google Cloud 控制台中一併查看及管理機群叢集，並使用支援機群的 GKE Enterprise 功能，大規模管理、控管及執行工作負載。如要查看適用於地端環境的機群功能完整清單，請參閱 GKE Enterprise 部署選項。
每個車隊叢集與 Google Cloud 的連線都由 Connect 代理程式管理，該代理程式會在 Google Distributed Cloud 安裝程序中部署。如要進一步瞭解這項代理程式的運作方式，請參閱 Connect 代理程式總覽。
[[["容易理解","easyToUnderstand","thumb-up"],["確實解決了我的問題","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["難以理解","hardToUnderstand","thumb-down"],["資訊或程式碼範例有誤","incorrectInformationOrSampleCode","thumb-down"],["缺少我需要的資訊/範例","missingTheInformationSamplesINeed","thumb-down"],["翻譯問題","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["上次更新時間：2025-07-31 (世界標準時間)。"],[],[],null,["Google Distributed Cloud is our solution that extends Google Cloud's infrastructure and\nservices into your data center. We offer Google Distributed Cloud in both connected and\nair-gapped configurations that run on Google-provided hardware. We also offer\nGoogle Distributed Cloud as a software-only product that runs on your own hardware.\nGoogle Distributed Cloud software can be installed on either VMware or bare metal. This\nguide is for Google Distributed Cloud software that runs on your own hardware in a\nVMware vSphere environment.\n\nGoogle Distributed Cloud is based on\n[Google Kubernetes Engine (GKE)](/kubernetes-engine/docs/concepts/kubernetes-engine-overview),\nwith its own Kubernetes package that extends GKE for use in an\non-premises environment. With Google Distributed Cloud you can create, manage, and\nupgrade GKE clusters on your own premises while using\nGoogle Cloud features, and deploy and operate containerized applications\non your clusters at scale using Google's infrastructure.\n\nInstalling Google Distributed Cloud software entitles you to use\nGKE Enterprise: an enterprise tier for GKE with\npowerful features for governing, managing, and operating containerized workloads\nat scale. You can find out more about GKE Enterprise and the\nfeatures available on VMware in the\n[GKE Enterprise (Anthos) technical overview](/kubernetes-engine/enterprise/docs/concepts/overview)\n\nThis page provides an overview of how Google Distributed Cloud works on VMware, giving\nyou the background you need before going on to a minimal or production\ninstallation.\n\nSupported versions\n\nThis documentation covers all supported versions of Google Distributed Cloud.\nWhere relevant, we also retain limited information for older, unsupported\nversions in this documentation. Version-specific differences in requirements and\nbehavior are noted in the documentation. Similarly, when a new feature becomes\navailable, the supported version for the feature is documented.\n\nFor a list of the supported minor versions and available patches, see\n[Versioning](/kubernetes-engine/distributed-cloud/vmware/docs/version-history).\n\nStarting with the 1.29 release, we no longer create a directory for the previous\nminor release. Differences in behavior and are noted in the documentation.\nSimilarly, when a new feature becomes available, the supported version for\nthe feature is documented.\n\nYou can find the complete documentation for an earlier version by adding the\nminor version number in the following URL: \n\n https://cloud.google.com/anthos/clusters/docs/on-prem/\u003cvar translate=\"no\"\u003eVERSION\u003c/var\u003e/\n\nReplace \u003cvar translate=\"no\"\u003eVERSION\u003c/var\u003e with a minor version from 1.0 to 1.16 and\ncopy the URL to the address bar in your browser.\n\nHow it works\n\nGoogle Distributed Cloud extends\n[GKE](/kubernetes-engine/docs/concepts/kubernetes-engine-overview)\nto let you create GKE clusters in a\n[vSphere environment](https://docs.vmware.com/en/VMware-vSphere/index.html)\non your own premises, and manage them in Google Cloud along with regular\nGKE clusters and clusters in other environments as part of a\n[fleet](/anthos/fleet-management/docs).\n\nBecause the Google Distributed Cloud software runs in your data center rather than on\nGoogle Cloud, it requires you to install some admin and control plane software\nin addition to the GKE software itself. The software that runs in\nyour data center is downloaded as part of the installation and upgrade\nprocesses.\n\nThe following diagram shows the simplified result of a completed installation.\n[](/static/kubernetes-engine/distributed-cloud/vmware/docs/images/diagram-overview.svg) Google Distributed Cloud architecture with one user cluster\n\nKey components\n\nThe following components make up a software-only installation on VMware of\nGoogle Distributed Cloud:\n\n- A user cluster is where the workloads that implement your applications run,\n like in GKE on Google Cloud. The nodes that run your workloads\n are called *worker nodes*. A user cluster also has one or more control plane\n nodes. In the preceding diagram, the user cluster has one control plane node.\n\n- The admin cluster manages one or more user clusters. In the preceding diagram,\n the admin cluster has three control plane nodes.\n\n- The admin workstation is a separate machine that includes the tools that\n cluster creators and developers need to manage their installation:\n\n - Running `gkectl` from the admin workstation lets you create and update clusters and perform some other administrative tasks\n - Running `kubectl` from the admin workstation lets you interact with your admin and user clusters, including deploying and managing workloads\n- The Google Cloud console provides a web interface for your Google Cloud project,\n including your clusters on VMware. You can perform a subset of administrative\n tasks, including cluster creation, from the Google Cloud console as an\n alternative to running commands on the admin workstation.\n\n- Cluster admins and developers use `kubectl` and virtual IP addresses (VIPs)\n to access the control planes in the admin and user clusters. You configure\n VIPs during cluster creation. Users and developers calling workloads in your\n user clusters use Service and Ingress VIPs. Each node in the installation\n also has its own IP address. You can learn more about IP planning for\n Google Distributed Cloud in [Plan your IP addresses](/kubernetes-engine/distributed-cloud/vmware/docs/how-to/plan-ip-addresses).\n\nConnecting to the fleet\n\nAll Google Distributed Cloud clusters are members of a [fleet](/anthos/fleet-management/docs):\na logical grouping of Kubernetes clusters. Fleets let your organization uplevel management from individual clusters to entire groups of clusters, and can help your teams adopt similar best practices to those used at Google. You can view and manage fleet clusters together in the Google Cloud console, and use fleet-enabled GKE Enterprise features to help you manage, govern, and operate your workloads at scale. You can see a complete list of available fleet features for on-premises environments in [GKE Enterprise deployment options](/anthos/deployment-options#features_available_on_anthos_clusters_outside_of_google_cloud).\n\nEach fleet cluster's connection to Google Cloud is managed by a Connect Agent, which is deployed as part of the Google Distributed Cloud installation process. You can learn more about how this agent works in the [Connect Agent overview](/anthos/fleet-management/docs/connect-agent).\n\nFleet membership is also used to manage Google Distributed Cloud pricing, as described in the next section.\n\nFor a deeper discussion of GKE Enterprise features and how they\nwork together, see the\n[GKE Enterprise technical overview](/anthos/docs/concepts/overview).\n\nPricing\n\nGKE clusters on-premises created as part of Google Distributed Cloud are\nbilled per vCPU as part of GKE Enterprise. You enable the\nEnterprise tier by enabling the\n[Anthos API](https://console.cloud.google.com/apis/library/anthos.googleapis.com)\nin your Google Cloud project..\n\nFor full pricing information, including how to contact sales, see\n[GKE pricing](/kubernetes-engine/pricing).\n\nInstalling Google Distributed Cloud on VMware\n\nBecause the Google Distributed Cloud software runs in your own infrastructure, it is\nhighly configurable to meet your particular organizational and use case needs:\nyou can choose from a range of supported load balancing modes, vSphere\nconfigurations, IP addressing options, security features, connectivity options,\nand more. This means that setting up Google Distributed Cloud involves making decisions\nbefore and during installation in consultation with your networking, vSphere,\nand application teams to ensure that your installation meets your needs. This\ndocumentation set includes guides to help your team make these decisions.\n\nHowever, if you just need to see Google Distributed Cloud in action, we also provide a\nbasic installation path for a small test installation where we've made a lot of\nthese choices for you, letting you quickly get a workload up and running.\n\nIn each case, the installation process is as follows:\n\n1. **Plan your installation**. Minimally this includes ensuring you can meet the resource and vSphere requirements for Google Distributed Cloud, as well as planning your IP addresses.\n2. **Set up your on-premises environment** to support Google Distributed Cloud, including setting up vSphere inventory objects and your connection to Google.\n3. **Set up Google Cloud resources**, including the Google Cloud project you will use when setting up and managing Google Distributed Cloud.\n4. **Create an admin workstation** with the resources and tools you need to create clusters.\n5. **Create an admin cluster** to create, manage, and update user clusters.\n6. **Create user clusters** to run your actual workloads.\n\nWhat's next?\n\n- To start a minimal proof-of-concept installation, see [Set up minimal infrastructure](/kubernetes-engine/distributed-cloud/vmware/docs/how-to/minimal-infrastructure).\n- To review some of the considerations needed to plan a Google Distributed Cloud installation, start a production installation, or both, see the [installation overview](/kubernetes-engine/distributed-cloud/vmware/docs/how-to/install-overview)."]]
