Google Cloud 控制台、Google Cloud CLI 或 Terraform，您可以在任何可連上 GKE On-Prem API 的電腦上執行這些工具。這些標準工具使用 GKE On-Prem API，該 API 會在 Google Cloud 基礎架構上執行。這些標準工具統稱為 GKE On-Prem API 用戶端。如要管理叢集的生命週期，GKE On-Prem API 必須在 Google Cloud中儲存叢集狀態的中繼資料，也就是您建立叢集時指定的 Google Cloud 區域。API 可透過這項中繼資料管理叢集生命週期，但不包含工作負載專屬資料。
無論使用哪種工具建立叢集，您收集並提供給工具的資訊都相同，例如叢集節點機器的 IP 位址和負載平衡器 VIP。
您可以根據用途和環境選擇最合適的工具。例如：
在開發環境中首次安裝時，您可能會想使用 Google Cloud 控制台，因為使用者介面會提供額外的指引和說明。
如果貴機構已使用 gcloud CLI 或 Terraform 管理其他 Google Cloud 資源，您可能也會想使用這些工具管理 Google Distributed Cloud。
如果貴機構有法規要求或限制，您可能需要減少對 Google Cloud 的依賴，並在管理員工作站使用 gkectl 建立叢集及管理叢集生命週期。
如果您使用 gkectl 建立叢集，系統預設會向 GKE On-Prem API 註冊該叢集。您也可以在建立叢集後註冊叢集，以便使用 GKE On-Prem API 用戶端。
GKE On-Prem API 用戶端限制
就支援的功能而言，gkectl 工具最為成熟。建議您在選擇時，先查看 GKE On-Prem API 用戶端的功能。下表列出 GKE On-Prem API 用戶端不支援的功能。
[[["容易理解","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-09-01 (世界標準時間)。"],[],[],null,["Google Distributed Cloud provides you a choice of tools to create clusters and\nmanage the cluster lifecycle operations (update, upgrade, and delete):\n\n- The command-line tool `gkectl`, which you run on your admin workstation in your on-premises data center. You create a [configuration file](/kubernetes-engine/distributed-cloud/vmware/docs/how-to/user-cluster-configuration-file-latest) that describes the cluster network, load balancing, and other cluster features. You specify this file on the command line to `gkectl`.\n- The Google Cloud console, Google Cloud CLI, or [Terraform](https://www.terraform.io), which you can run from any computer that has network connectivity to the GKE On-Prem API. These standard tools use the [GKE On-Prem API](/kubernetes-engine/distributed-cloud/reference/on-prem-api-overview), which runs on Google Cloud infrastructure. Collectively, the standard tools are referred to as the *GKE On-Prem API clients*. To manage the lifecycle of your clusters, the GKE On-Prem API must store metadata about your cluster's state in Google Cloud, in the Google Cloud region that you specify when creating the cluster. This metadata lets the API manage the cluster lifecycle and doesn't include workload-specific data.\n\nNo matter which tool you use to create clusters, the information that\nyou gather and provide to the tool, such as the IP addresses\nof cluster node machines and load balancer VIPs, is the same.\n\nThis selection lets you choose the best tool for your use case and\nenvironment. For example:\n\n- For your first installations in a development environment, you might want to use the Google Cloud console because the user interface provides additional guidance and help.\n- If your organization already uses the gcloud CLI or Terraform to manage other Google Cloud resources, you will probably want to use these tools for Google Distributed Cloud as well.\n- If your organization has regulatory requirements or restrictions, you might need to limit your reliance on Google Cloud and use `gkectl` on your admin workstation to create clusters and manage cluster lifecycle.\n\nIf you create a cluster with `gkectl`, it will be enrolled with the\nGKE On-Prem API by default. You can also\n[enroll the cluster](/kubernetes-engine/distributed-cloud/vmware/docs/how-to/enroll-cluster) after it is created,\nwhich lets you use the GKE On-Prem API clients.\n\nLimitations with the GKE On-Prem API clients\n\nThe `gkectl` tool is the most mature as far as features that it supports. We\nrecommend that you review the capabilities for the GKE On-Prem API clients when\nmaking a choice. The following list shows the features that are not supported by\nthe GKE On-Prem API clients.\n\n- [Advanced clusters](/kubernetes-engine/distributed-cloud/vmware/docs/concepts/advanced-clusters)\n- Secret management and rotation\n- Certificate rotation\n- Authentication\n- Usage metering\n- Application level logging and monitoring\n- Advanced networking\n- Windows node pools\n\nThe following list describes additional limitations with the GKE On-Prem API\nclients:\n\n- The gcloud CLI isn't supported for any admin cluster lifecycle\n operation. You can use `gkectl`, the console, the\n gcloud CLI, or Terraform to create admin clusters.\n\n- The `gkectl` command-line tool is the only tool available for upgrading,\n updating, and deleting admin clusters.\n\n- Only `gkectl` and Terraform support using a\n [private registry](/kubernetes-engine/distributed-cloud/vmware/docs/how-to/private-registry).\n\n- The kind of load balancer for an admin cluster and its user clusters must be\n the same. The only exception is if the admin cluster uses Seesaw, then the\n user clusters can use MetalLB. If you want your admin and user clusters to use\n different kinds of load balancers, you must create the clusters using\n `gkectl`.\n\n- When you create a user cluster using the Google Cloud console, all the\n [`vCenter` settings](/kubernetes-engine/distributed-cloud/vmware/docs/how-to/user-cluster-configuration-file-latest#vcenter-section)\n are inherited from the admin cluster. If you need a user cluster to have\n different `vCenter` settings from its admin cluster, use the\n gcloud CLI, Terraform, or `gkectl` to create the user cluster.\n\nCheck on these limitations from time to time as the GKE On-Prem API clients\nevolve."]]
