完成叢集節點機器的設定、網路和其他必要條件後，即可準備安裝 Google Distributed Cloud。接下來，請決定要建立哪些類型的叢集，並選擇要使用的工具。
選擇叢集類型
您可以在 Google Distributed Cloud 中建立不同類型的叢集，包括管理員叢集 (用於控管叢集資源) 和使用者叢集 (用於執行工作負載)。如果您在同一個資料中心有多個叢集，且想從集中式位置管理這些叢集，或是需要隔離不同團隊或開發與生產工作負載，建議您部署管理員和使用者叢集。
您也可以將 Google Distributed Cloud 做為單一獨立叢集執行，同時做為使用者叢集和管理員叢集。獨立叢集支援邊緣設定檔，這個設定檔大幅減少了系統資源需求，建議資源高度受限的邊緣裝置使用。此外，您還可以使用 Google Distributed Cloud 建立混合式叢集，結合管理工作和工作負載，並控管其他使用者叢集。
建立新叢集前，請先瞭解影響可擴充性的維度。部分維度 (例如可為叢集中的 Pod 保留的 IP 位址數量 clusterNetwork.pods.cidrBlocks) 無法變更，因此您需要在建立叢集時規劃這些維度。如要進一步瞭解可擴充性維度，以及如何擴充叢集，請參閱擴充 Google Distributed Cloud 叢集。如要瞭解叢集最大設定的限制和建議，請參閱配額與限制。
[[["容易理解","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,["# Cluster creation overview\n\nWhen you have finished setting up cluster node machines,\n[your network](/kubernetes-engine/distributed-cloud/bare-metal/docs/how-to/plan-ip-addresses), and\nthe other [prerequisites](/kubernetes-engine/distributed-cloud/bare-metal/docs/installing/install-prereq), you're\nalmost ready to install Google Distributed Cloud. The next step is to decide what\nkinds of clusters to create and choose which tool to use.\n\nChoose a cluster type\n---------------------\n\nYou can create different kinds of clusters in Google Distributed Cloud, including\n**admin** clusters (to control the resources of your clusters) and **user**\nclusters (to run workloads). We recommend admin and user cluster deployments\nif you have multiple clusters in the same data center that you want to manage\nfrom a centralized place, and for larger deployments that need isolation between\ndifferent teams or between development and production workloads.\n\nYou can also run Google Distributed Cloud as a single **standalone** cluster,\nwhich serves as a user cluster and as an admin cluster. A standalone cluster\nsupports the edge profile, which has significantly reduced system resource\nrequirements and is recommended for edge devices with high resource constraints.\nIn addition, Google Distributed Cloud lets you create **hybrid** clusters that\ncombine administration tasks and workloads, as well as controlling other user\nclusters.\n\nEach of these configurations has their own advantages and benefits. For more\ninformation on deciding which configuration to develop, see\n[Choose a deployment model](/kubernetes-engine/distributed-cloud/bare-metal/docs/installing/install-prep).\n\nChoose a tool to create clusters\n--------------------------------\n\nYou have your choice of tools for creating clusters and managing\ncluster lifecycle:\n\n- The command-line tool `bmctl`, which you run on your admin workstation in your on-premises data center.\n- The Google Cloud console, Google Cloud CLI, or [Terraform](https://www.terraform.io/). These standard tools use the GKE On-Prem API, which runs on Google Cloud infrastructure, and collectively they are referred to as the *GKE On-Prem API clients*.\n\nFor information on deciding which tool best suits your needs, see\n[Choose a tool to create clusters](/kubernetes-engine/distributed-cloud/bare-metal/docs/installing/cluster-lifecycle-management-tools).\n\nMore information\n----------------\n\nFor more information on creating and configuring clusters, see the\nfollowing:\n\n- Admin clusters:\n\n - [Create admin clusters using GKE On-Prem API clients](/kubernetes-engine/distributed-cloud/bare-metal/docs/installing/creating-clusters/create-admin-cluster-api)\n - [Create admin clusters using `bmctl`](/kubernetes-engine/distributed-cloud/bare-metal/docs/installing/creating-clusters/admin-cluster-creation)\n- User clusters\n\n - [Create user clusters using GKE On-Prem API clients](/kubernetes-engine/distributed-cloud/bare-metal/docs/installing/creating-clusters/create-user-cluster-api)\n - [Create user clusters using `bmctl`](/kubernetes-engine/distributed-cloud/bare-metal/docs/installing/creating-clusters/user-cluster-creation)\n- [Create standalone clusters](/kubernetes-engine/distributed-cloud/bare-metal/docs/installing/creating-clusters/standalone-cluster-creation)\n\n- [Create hybrid clusters](/kubernetes-engine/distributed-cloud/bare-metal/docs/installing/creating-clusters/hybrid-cluster-creation)\n\nAbout the creation process\n--------------------------\n\nThe cluster creation process includes preflight checks and machine\ninitialization. If cluster creation fails after the machine initialization phase\n(even if preflight checks passed without errors), you must\n[delete the cluster](/kubernetes-engine/distributed-cloud/bare-metal/docs/how-to/reset-nodes). This returns the node to\na clean state. After deleting the cluster, you can re-attempt to create the\ncluster after making any needed configuration changes.\n\nThe cluster creation process runs health checks when the cluster has been\ncreated. This last step verifies that the cluster is in good operating\ncondition. If the cluster doesn't pass all health checks, the create operation\nfails. When all health checks pass, the create operation finishes successfully.\n\nPlan for scalability\n--------------------\n\nBefore you create a new cluster, you need to understand the dimensions that\naffect scalability. Some dimensions, such as the number of IP addresses that you\ncan reserve for Pods in your cluster (`clusterNetwork.pods.cidrBlocks`), are\nimmutable, so you need to plan for them when you create a cluster. For more\ninformation about scalability dimensions and how to scale up a cluster, see\n[Scale up Google Distributed Cloud\nclusters](/kubernetes-engine/distributed-cloud/bare-metal/docs/how-to/scale). For information about some of the\nrestrictions and recommendations for maximum settings for your cluster, see\n[Quotas and limits](/kubernetes-engine/distributed-cloud/bare-metal/docs/limits)."]]
