本頁說明如何使用 Google Cloud 控制台，調查建立 Google Distributed Cloud 使用者叢集時發生的問題。
GKE On-Prem API 是 Google Cloud 代管的 API，可讓您使用 Terraform 和標準Google Cloud 工具，管理內部部署叢集的生命週期。GKE On-Prem API 會在 Google Cloud的基礎架構中執行。Terraform、 Google Cloud 控制台和 Google Cloud CLI 都是 API 的用戶端，可透過 API 在資料中心建立、更新、升級及刪除叢集。如果您使用標準用戶端建立叢集，該叢集會註冊 GKE On-Prem API，這表示您可以使用標準用戶端管理叢集的生命週期 (少數例外)。
- Validation Category: Network Configuration
- [FAILURE] CIDR, VIP and static IP (availability and overlapping): user: user
cluster control plane VIP "10.251.133.132" overlaps with
example-cluster1/control plane VIP "10.251.133.132"
您無法在Google Cloud 控制台的「叢集詳細資料」頁面中，編輯「負載平衡器」部分中的「控制層 VIP」和「Ingress VIP」等欄位。如要修正 IP 位址衝突問題，請刪除並重新建立叢集：
[[["容易理解","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-08-31 (世界標準時間)。"],[],[],null,["This page shows you how to investigate issues creating an\nGoogle Distributed Cloud user cluster in the Google Cloud console.\n\nThe GKE On-Prem API is a Google Cloud-hosted API that lets you manage the\nlifecycle of your on-premises clusters using Terraform and standard\nGoogle Cloud tools. The GKE On-Prem API runs in Google Cloud's\ninfrastructure. Terraform, the Google Cloud console, and the Google Cloud CLI are\nclients of the API, and they use the API to create, update, upgrade, and\ndelete clusters in your data center. If you created the cluster using\na standard client, the cluster is *enrolled* in the GKE On-Prem API, which\nmeans you can use the standard clients to manage the lifecycle of the cluster\n(with some exceptions).\n\n\nCluster creation errors\n\nThis section describes some errors that happen during cluster creation in the\nGoogle Cloud console.\n\nResource already exists error\n\nUser cluster creation fails with an error message similar to the following: \n\n Resource 'projects/1234567890/[...]/user-cluster1'\n already exists\n Request ID: 129290123128705826\n\nThis error message indicates that the cluster name is already in use.\n\nOne solution to fix this is issue is to delete and recreate the cluster:\n\n1. [Delete the cluster](/kubernetes-engine/distributed-cloud/bare-metal/docs/how-to/reset-nodes).\n2. Create the cluster again with a another name that doesn't conflict with an existing cluster.\n\nConflicting IP addresses error\n\nUser cluster creation fails with an error message similar to the following: \n\n - Validation Category: Network Configuration\n - [FAILURE] CIDR, VIP and static IP (availability and overlapping): user: user\n cluster control plane VIP \"10.251.133.132\" overlaps with\n example-cluster1/control plane VIP \"10.251.133.132\"\n\nYou can't edit fields such as the **Control plane VIP** and the **Ingress VIP**\nin the **Load balancer** section of the **Cluster details** page in the\nGoogle Cloud console. To fix conflicting IP addresses, delete and recreate the\ncluster:\n\n1. [Delete the cluster](/kubernetes-engine/distributed-cloud/bare-metal/docs/how-to/reset-nodes).\n2. Create the cluster again with IP addresses that don't conflict with an existing cluster.\n\nRemove unhealthy clusters\n\nA cluster can get in an unhealthy state for many reasons, such as:\n\n- Connectivity issues with the [Connect Agent](/anthos/fleet-management/docs/connect-agent) or the on-premises environment.\n- The admin cluster for a user cluster was deleted, or there are connectivity issues between the admin and user clusters.\n\nIf the console is unable to delete a cluster, use\ngcloud CLI commands to delete Google Cloud resources from\nunhealthy clusters. If you haven't updated the gcloud CLI recently,\nrun the following command to update the components:\n\n```\ngcloud components update\n```\n\nNext, delete the Google Cloud resources. \n\nUser cluster\n\n1. Delete the user cluster:\n\n ```\n gcloud container bare-metal clusters delete USER_CLUSTER_NAME \\\n --project=PROJECT_ID \\\n --location=REGION \\\n --force \\\n --allow-missing \\\n --ignore-errors\n ```\n\n Replace the following:\n - \u003cvar translate=\"no\"\u003eUSER_CLUSTER_NAME\u003c/var\u003e: The name of the user cluster\n to delete.\n\n - \u003cvar translate=\"no\"\u003ePROJECT_ID\u003c/var\u003e: The ID of the project that\n the cluster is registered to.\n\n - \u003cvar translate=\"no\"\u003eREGION\u003c/var\u003e: The Google Cloud location associated with\n the user cluster. The location is displayed in the\n console.\n\n The `--force` flag deletes a cluster that has node pools.\n Without the `--force` flag, you have to\n [delete the node pools](/sdk/gcloud/reference/container/bare-metal/node-pools/delete)\n first, and then delete the cluster.\n\n The `--allow-missing` flag allows the command to continue if the\n cluster isn't found.\n\n The `--ignore-errors` flag removes Google Cloud resources when the\n admin and user clusters are unreachable.\n\n This command deletes the cluster if it exists and removes both\n GKE On-Prem API and fleet membership resources from Google Cloud.\n2. Confirm that the GKE On-Prem API resources have been deleted:\n\n ```\n gcloud container bare-metal clusters list \\\n --project=PROJECT_ID \\\n --location=-\n ```\n\n When you set `--location=-`, that means to list all clusters in all\n regions. If you need to scope down the list, set `--location` to a\n [specific region](/kubernetes-engine/distributed-cloud/bare-metal/docs/reference/supported-regions-on-prem-api).\n3. Confirm that the fleet membership resources have been deleted:\n\n ```\n gcloud container fleet memberships list \\\n --project=PROJECT_ID\n ```\n\nAdmin cluster\n\n1. If you enrolled the admin cluster in the GKE On-Prem API, unenroll it:\n\n ```\n gcloud container bare-metal admin-clusters unenroll ADMIN_CLUSTER_NAME \\\n --project=PROJECT_ID \\\n --location=REGION \\\n --allow-missing --ignore-errors \n ```\n\n Replace the following:\n - \u003cvar translate=\"no\"\u003eADMIN_CLUSTER_NAME\u003c/var\u003e: The name of the admin cluster.\n - \u003cvar translate=\"no\"\u003ePROJECT_ID\u003c/var\u003e: The ID of the fleet host project.\n - \u003cvar translate=\"no\"\u003eREGION\u003c/var\u003e: The Google Cloud region.\n\n The `--allow-missing` flag unenrolls the cluster if the fleet membership\n isn't found.\n\n The `--ignore-errors` flag removes\n Google Cloud resources when the admin and user clusters are unreachable.\n\n This command removes the GKE On-Prem API resources from Google Cloud.\n2. Remove the cluster from the fleet:\n\n ```\n gcloud container fleet memberships delete ADMIN_CLUSTER_NAME \\\n --project=PROJECT_ID \\\n --location=global\n ```\n\n This command removes fleet membership resources from Google Cloud.\n3. Confirm that the GKE On-Prem API resources have been deleted:\n\n ```\n gcloud container fleet memberships delete ADMIN_CLUSTER_NAME --project=FLEET_HOST_PROJECT_ID\n ```\n\n When you set `--location=-`, that means to list all clusters in all\n regions. If you need to scope down the list, set `--location` to a\n [specific region](/kubernetes-engine/distributed-cloud/bare-metal/docs/reference/supported-regions-on-prem-api).\n4. Confirm that the fleet membership resources have been deleted:\n\n ```\n gcloud container fleet memberships list \\\n --project=PROJECT_ID\n ```\n\nWhat's next\n\nIf you need additional assistance, reach out to\n\n[Cloud Customer Care](/support-hub).\nYou can also see\n[Getting support](/kubernetes-engine/distributed-cloud/bare-metal/docs/getting-support) for more information about support resources, including the following:\n\n- [Requirements](/kubernetes-engine/distributed-cloud/bare-metal/docs/getting-support#intro-support) for opening a support case.\n- [Tools](/kubernetes-engine/distributed-cloud/bare-metal/docs/getting-support#support-tools) to help you troubleshoot, such as your environment configuration, logs, and metrics.\n- Supported [components](/kubernetes-engine/distributed-cloud/bare-metal/docs/getting-support#what-we-support)."]]
