Stay organized with collections
Save and categorize content based on your preferences.
Deleting a Connect cluster erases all associated data, including connector
configurations stored in its primary Kafka cluster. This action is irreversible.
To delete a Connect cluster, you can use the Google Cloud console,
the gcloud CLI, the client library, or the
Managed Kafka API. You can't use the open source Apache Kafka API to
delete a Connect cluster.
Required roles and permissions to delete a Connect cluster
This predefined role contains
the permissions required to delete a Connect cluster. To see the exact permissions that are
required, expand the Required permissions section:
Required permissions
The following permissions are required to delete a Connect cluster:
Grant the delete a Connect cluster permission on the Connect cluster:
managedkafka.connectClusters.delete
Grant the list Connect clusters permission on the specified location. This permission is only required for deleting a Connect cluster using the Google Cloud console:
managedkafka.connectClusters.list
Understand data loss implications: Deleting a Connect cluster erases
all data stored within the Connect cluster itself. This includes the
following:
Connectors and their configurations
Any other data directly managed by the Connect cluster
Deleting a Connect cluster
does not delete data in your source or target
Kafka clusters. If you're using a source connector to move data to a
Kafka topic, deleting the Connect cluster does not delete the data
that is already published to that Kafka topic. Similarly, deleting a
Connect cluster does not delete the Kafka clusters that the Connect
cluster is associated with.
Plan for service disruption: Any applications or services
depending on data read or written by the Connect cluster might experience disruptions.
Plan for this service disruption before deleting the cluster.
Review billing implications: You stop incurring charges for the cluster
after you delete it. You might still be billed for resources used until
deletion.
Expect asynchronous operation: Cluster deletion is asynchronous by
default. The command returns immediately, and you can track the deletion
progress separately.
Console
In the Google Cloud console, go to the Connect clusters page.
At the bottom of the Google Cloud console, a
Cloud Shell
session starts and displays a command-line prompt. Cloud Shell is a shell environment
with the Google Cloud CLI
already installed and with values already set for
your current project. It can take a few seconds for the session to initialize.
[[["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,["# Delete a Connect cluster\n\n| **Preview**\n|\n|\n| This product or 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 products and 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\nDeleting a Connect cluster erases all associated data, including connector\nconfigurations stored in its primary Kafka cluster. This action is irreversible.\n\nTo delete a Connect cluster, you can use the Google Cloud console,\nthe gcloud CLI, the client library, or the\nManaged Kafka API. You can't use the open source Apache Kafka API to\ndelete a Connect cluster.\n\nRequired roles and permissions to delete a Connect cluster\n----------------------------------------------------------\n\n\nTo get the permissions that\nyou need to delete a Connect cluster,\n\nask your administrator to grant you the\n\n\n[Managed Kafka Connect Cluster Editor](/iam/docs/roles-permissions/managedkafka#managedkafka.connectClusterEditor) (`roles/managedkafka.connectClusterEditor`)\nIAM role on your project.\n\n\nFor more information about granting roles, see [Manage access to projects, folders, and organizations](/iam/docs/granting-changing-revoking-access).\n\n\nThis predefined role contains\n\nthe permissions required to delete a Connect cluster. To see the exact permissions that are\nrequired, expand the **Required permissions** section:\n\n\n#### Required permissions\n\nThe following permissions are required to delete a Connect cluster:\n\n- Grant the delete a Connect cluster permission on the Connect cluster: ` ``managedkafka.connectClusters.delete`\n- Grant the list Connect clusters permission on the specified location. This permission is only required for deleting a Connect cluster using the Google Cloud console: ` ``managedkafka.connectClusters.list`\n\n\nYou might also be able to get\nthese permissions\nwith [custom roles](/iam/docs/creating-custom-roles) or\nother [predefined roles](/iam/docs/roles-overview#predefined).\n\nFor more information about the Managed Kafka Connect Cluster Editor role, see\n[Managed Service for Apache Kafka predefined roles](/managed-service-for-apache-kafka/docs/access-control#predefined-roles).\n\nDelete a Connect cluster\n------------------------\n\n- **Understand data loss implications:** Deleting a Connect cluster erases\n all data stored *within the Connect cluster itself*. This includes the\n following:\n\n - Connectors and their configurations\n\n - Any other data directly managed by the Connect cluster\n\n Deleting a Connect cluster\n does *not* delete data in your source or target\n Kafka clusters. If you're using a source connector to move data to a\n Kafka topic, deleting the Connect cluster does not delete the data\n that is already published to that Kafka topic. Similarly, deleting a\n Connect cluster does not delete the Kafka clusters that the Connect\n cluster is associated with.\n- **Plan for service disruption:** Any applications or services\n depending on data read or written by the Connect cluster might experience disruptions.\n Plan for this service disruption before deleting the cluster.\n\n- **Review billing implications:** You stop incurring charges for the cluster\n after you delete it. You might still be billed for resources used until\n deletion.\n\n- **Expect asynchronous operation:** Cluster deletion is asynchronous by\n default. The command returns immediately, and you can track the deletion\n progress separately.\n\n### Console\n\n1. In the Google Cloud console, go to the **Connect clusters** page.\n\n [Go to Connect clusters](https://console.cloud.google.com/managedkafka/connectClusters)\n2. Select the Connect cluster that you want to delete. You can select more than one.\n\n3. Click **Delete**.\n\n### gcloud\n\n1. In the Google Cloud console, activate Cloud Shell.\n\n [Activate Cloud Shell](https://console.cloud.google.com/?cloudshell=true)\n\n\n At the bottom of the Google Cloud console, a\n [Cloud Shell](/shell/docs/how-cloud-shell-works)\n session starts and displays a command-line prompt. Cloud Shell is a shell environment\n with the Google Cloud CLI\n already installed and with values already set for\n your current project. It can take a few seconds for the session to initialize.\n2. Use the [`gcloud alpha managed-kafka connect-clusters delete`](/sdk/gcloud/reference/alpha/managed-kafka/connect-clusters/delete) command to delete Connect clusters:\n\n \u003cbr /\u003e\n\n ```bash\n gcloud alpha managed-kafka connect-clusters delete CONNECT_CLUSTER \\\n --location=LOCATION [--async]\n ```\n\n Replace the following:\n - \u003cvar translate=\"no\"\u003eCONNECT_CLUSTER\u003c/var\u003e: The ID of the Connect cluster you want to delete.\n\n - \u003cvar translate=\"no\"\u003eLOCATION\u003c/var\u003e: The location of the Connect cluster.\n\n The following flag is optional:\n - `--async`: Return immediately, without waiting for the operation in progress to complete.\n\n For example, to delete a Connect cluster named `my-connect-cluster` in the `us-central1` location, you would run: \n\n ```bash\n gcloud alpha managed-kafka connect-clusters delete \\\n my-connect-cluster --location=us-central1\n ```\n\n \u003cbr /\u003e\n\n\u003cbr /\u003e\n\nWhat's next?\n------------\n\n- [List all Connect clusters](/managed-service-for-apache-kafka/docs/connect-cluster/list-connect-cluster)\n\n- [View details about a Connect cluster](/managed-service-for-apache-kafka/docs/connect-cluster/view-connect-cluster)\n\n- [Update a Connect cluster](/managed-service-for-apache-kafka/docs/connect-cluster/update-connect-cluster)\n\n- [An overview of connectors](/managed-service-for-apache-kafka/docs/connect-cluster/connectors-overview)\n\n*Apache Kafka® is a registered\ntrademark of The Apache Software Foundation or its affiliates in the United\nStates and/or other countries.*"]]
