[[["容易理解","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-04 (世界標準時間)。"],[[["\u003cp\u003eDeleting an AlloyDB cluster is possible through the Google Cloud console or the gcloud CLI, but ongoing backup operations will delay the deletion until they are complete.\u003c/p\u003e\n"],["\u003cp\u003eYou must have proper IAM roles, such as AlloyDB Admin, Owner, or Editor, and the project must have AlloyDB access enabled to delete a cluster.\u003c/p\u003e\n"],["\u003cp\u003eThe Google Cloud console cannot delete a cluster if it still has instances, requiring the gcloud CLI with the \u003ccode\u003e--force\u003c/code\u003e option to override and delete all instances within the cluster first.\u003c/p\u003e\n"],["\u003cp\u003eThe \u003ccode\u003egcloud alloydb clusters delete\u003c/code\u003e command is used to delete a cluster, requiring the cluster ID, region ID, and project ID as parameters, with the \u003ccode\u003e--force\u003c/code\u003e option to also remove any instances within that cluster.\u003c/p\u003e\n"]]],[],null,["# Delete a cluster\n\nThis page describes how to delete an AlloyDB cluster.\n| **Caution:** If there is a cluster backup operation on the cluster that you want to delete, then the cluster deletion is queued until the backup operation completes. The cluster continues to be billed until the cluster status changes from `ready` to `deleting`.\n\n\nBefore you begin\n----------------\n\n- The Google Cloud project you are using must have been [enabled to access AlloyDB](/alloydb/docs/project-enable-access).\n- You must have one of these IAM roles in the Google Cloud project you are using:\n - `roles/alloydb.admin` (the AlloyDB Admin predefined IAM role)\n - `roles/owner` (the Owner basic IAM role)\n - `roles/editor` (the Editor basic IAM role)\n\n If you don't have any of these roles, contact your Organization Administrator to request\n access.\n\n\u003cbr /\u003e\n\nProcedure\n---------\n\n### Console\n\n1. In the Google Cloud console, go to the **Clusters** page.\n\n [Go to Clusters](https://console.cloud.google.com/alloydb/clusters)\n2. Click a cluster in the **Resource Name** column.\n3. In the **Overview** page of your cluster, click **Delete cluster**.\n4. In the **Delete cluster** dialog that appears, enter your cluster ID.\n5. Click **Delete**.\n\nYou can't delete an AlloyDB cluster that contains any instances using the Google Cloud console.\nTo override this default behavior, use the gcloud CLI to specify the\n[`--force` option](/sdk/gcloud/reference/alloydb/clusters/delete) in the `clusters delete` command.\n\n### gcloud\n\nTo use the gcloud CLI, you can\n[install and initialize](/sdk/docs/install) the Google Cloud CLI, or you\ncan use [Cloud Shell](/shell/docs/using-cloud-shell).\n\nUse the `clusters delete` command to delete a cluster. \n\n```\ngcloud alloydb clusters delete CLUSTER_ID \\\n --region=REGION_ID \\\n --project=PROJECT_ID\n```\n\n- \u003cvar translate=\"no\"\u003eCLUSTER_ID\u003c/var\u003e: The ID of the cluster.\n- \u003cvar translate=\"no\"\u003eREGION_ID\u003c/var\u003e: The region where the cluster is placed.\n- \u003cvar translate=\"no\"\u003ePROJECT_ID\u003c/var\u003e: The ID of the project where the cluster is placed.\n\n#### Deleting a cluster that contains instances\n\nAttempts to delete an AlloyDB cluster that contains any\ninstances will fail. To override this behavior, specify the\n`--force` option in the `clusters delete` command to\ndirect AlloyDB to delete all instances in the cluster and then\ndelete the cluster itself; for example: \n\n```\ngcloud alloydb clusters delete CLUSTER_ID \\\n --force \\\n --region=REGION_ID \\\n --project=PROJECT_ID\n```"]]
