Stay organized with collectionsSave and categorize content based on your preferences.
Detaching a cluster means deregistering it from Google CloudFleet managementand removing the associated
software from your cluster. You can detach the cluster with the Google Cloud CLI
or the Google Cloud console.
Providing the optional flag--ignore-errorsforces the cluster
to detach even if some in-cluster resources can't be deleted. Including the
optional--allow-missingflag means that the delete request returns
a success code even if the cluster can't be found:
This feature is subject to the "Pre-GA Offerings Terms" in the General Service Terms section
of theService Specific Terms.
Pre-GA features are available "as is" and might have limited support.
For more information, see thelaunch stage descriptions.
In the Google Cloud console, go to theGoogle Kubernetes Engine clusters
overviewpage.
Select the Google Cloud project that the cluster is in.
Click the name of the cluster you want to detach, and then selectView more detailsin the side panel.
Near the top of the window, clickdeleteDelete.
When prompted to confirm, enter the name of the cluster and
clickConfirm.
When you detach a cluster, all Google Cloud resources related to the cluster,
such as the fleet membership resources and workload identity pool OIDC
providers are deleted. Any features installed in
your cluster, such as Config Sync and Cloud Service Mesh, are also deleted. The
Kubernetes cluster itself isn't deleted.
[[["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-09-04 UTC."],[],[],null,["Detaching a cluster means deregistering it from Google Cloud\n[Fleet management](/anthos/fleet-management/docs) and removing the associated\nsoftware from your cluster. You can detach the cluster with the Google Cloud CLI\nor the Google Cloud console. \n\ngcloud CLI\n\nTo detach a cluster, use the\n[`gcloud container attached clusters delete` command](/sdk/gcloud/reference/container/attached/clusters/delete).\n\nProviding the optional flag `--ignore-errors` forces the cluster\nto detach even if some in-cluster resources can't be deleted. Including the\noptional `--allow-missing` flag means that the delete request returns\na success code even if the cluster can't be found:\n\n```\ngcloud container attached clusters delete CLUSTER_NAME \\\n --ignore-errors \\\n --allow-missing \\\n --location=GOOGLE_CLOUD_REGION\n```\n\nReplace the following:\n\n- \u003cvar translate=\"no\"\u003eCLUSTER_NAME\u003c/var\u003e: the name of your cluster\n- \u003cvar translate=\"no\"\u003eGOOGLE_CLOUD_REGION\u003c/var\u003e: the name of the Google Cloud region administering your cluster\n\nFor more information, see\n[gcloud container attached clusters delete](/sdk/gcloud/reference/container/attached/clusters/delete).\n\nConsole\n\n\n| **Preview**\n|\n|\n| This feature is subject to the \"Pre-GA Offerings Terms\" in the General Service Terms section\n| of the [Service Specific Terms](/terms/service-terms#1).\n|\n| Pre-GA features are available \"as is\" and might have limited support.\n|\n| For more information, see the\n| [launch stage descriptions](/products#product-launch-stages).\n\n\u003cbr /\u003e\n\n1. In the Google Cloud console, go to the **Google Kubernetes Engine clusters\n overview** page.\n\n [Go to GKE clusters](https://console.cloud.google.com/kubernetes/list/overview)\n2. Select the Google Cloud project that the cluster is in.\n\n3. Click the name of the cluster you want to detach, and then select\n **View more details** in the side panel.\n\n4. Near the top of the window, click delete **Delete**.\n\n5. When prompted to confirm, enter the name of the cluster and\n click **Confirm**.\n\nWhen you detach a cluster, all Google Cloud resources related to the cluster,\nsuch as the fleet membership resources and workload identity pool OIDC\nproviders are deleted. Any features installed in\nyour cluster, such as Config Sync and Cloud Service Mesh, are also deleted. The\nKubernetes cluster itself isn't deleted."]]
