DOC-1565 Disable KC with Cloud API (#381)

* DOC-1565 Disable KC with Cloud API

* minor edit

* minor edits

* update What's New

* incorporate review comments

* review comments

* update text for authenticating to API

* add steps to verify if KC is enabled

* Masa's example

* update to ${AUTH_TOKEN}

* gah, updated to $AUTH_TOKEN

Author: micheleRP

modules/ROOT/nav.adoc

@@ -379,6 +379,7 @@
 ** xref:develop:managed-connectors/index.adoc[Kafka Connect]
 *** xref:develop:managed-connectors/converters-and-serialization.adoc[Converters and serialization]
 *** xref:develop:managed-connectors/monitor-connectors.adoc[Monitor Connectors]
+*** xref:develop:managed-connectors/disable-kc.adoc[]
 *** xref:develop:managed-connectors/transforms.adoc[Single Message Transforms]
 *** xref:develop:managed-connectors/sizing-connectors.adoc[Sizing Connectors]
 *** xref:develop:managed-connectors/create-s3-sink-connector.adoc[AWS S3 Sink Connector]

modules/develop/pages/managed-connectors/converters-and-serialization.adoc

@@ -1,5 +1,5 @@
 = Converters and Serialization
-:description: Use converters to handle the serialization and deserialization of data between a Redpanda topic and a managed connector.
+:description: Use converters to handle the serialization and deserialization of data between a Redpanda topic and an external system with Kafka Connect.
 :page-aliases: deploy:deployment-option/cloud/managed-connectors/converters-and-serialization.adoc
 
 include::shared:partial$kafka-connect.adoc[]

modules/develop/pages/managed-connectors/disable-kc.adoc

@@ -0,0 +1,64 @@
+= Disable Kafka Connect
+:description: Learn how to disable Kafka Connect using the Cloud API.
+
+Kafka Connect is disabled by default on new clusters. If you previously enabled Kafka Connect on a cluster and want to disable it, you can use the xref:manage:api/cloud-api-overview.adoc[Cloud API]. 
+
+NOTE: Redpanda Support does not manage or monitor Kafka Connect, but Support can enable the feature for your account.
+
+== Verify Kafka Connect is enabled
+
+If Kafka Connect is enabled on your cluster, you will see it configured on the *Connect* page in the Redpanda Cloud UI.
+
+You can also verify with the Cloud API: 
+
+[,bash]
+----
+curl -sX GET "https://api.redpanda.com/v1/clusters/{cluster.id}" \
+ -H "Authorization: Bearer $AUTH_TOKEN" \
+ -H 'accept: application/json'  | jq -r '.cluster.kafka_connect' 
+----  
+
+Replace `{cluster.id}` with your actual cluster ID. You can find the cluster ID in the Redpanda Cloud UI. Look in the **Details** section of the cluster overview.
+
+If Kafka Connect is enabled, the response will show:
+
+[,bash]
+----
+  "enabled": true
+----  
+
+== Prerequisites
+
+- You have the cluster ID of a cluster that has Kafka Connect enabled. 
+- You have a valid bearer token for the Cloud API. For details, see xref:manage:api/cloud-api-authentication.adoc[Authenticate to the API]. 
+
+IMPORTANT: Make sure to stop any active connectors gracefully before disabling Kafka Connect to avoid data loss or incomplete processing.
+
+== Disable Kafka Connect
+
+After you are authenticated to the Cloud API, make a xref:api:ROOT:cloud-controlplane-api.adoc#patch-/v1/clusters/-cluster.id-[`PATCH /v1/clusters/{cluster.id}`] request, replacing `{cluster.id}` with your actual cluster ID.
+
+[,bash]
+----
+curl -X PATCH "https://api.redpanda.com/v1/clusters/{cluster.id}" \
+  -H "Authorization: Bearer $AUTH_TOKEN" \
+  -H "Content-Type: application/json" \
+  -d '{"kafka_connect":{"enabled":false}}'
+----
+
+The `PATCH` request returns the ID of a long-running operation. You can check the status of the operation by polling the xref:api:ROOT:cloud-controlplane-api.adoc#get-/v1/operations/-id-[`GET /operations/{id}`] endpoint:
+
+[,bash]
+----
+curl -X GET "https://api.redpanda.com/v1/operations/{operation.id}" \
+  -H "Authorization: Bearer $AUTH_TOKEN" \
+  -H "Content-Type: application/json"
+----
+
+When the operation is complete, the status will show `"state": "STATE_COMPLETED"`. You can verify that Kafka Connect has been disabled by running the verification command from the previous section. The response should show:
+
+[,bash]
+----
+  "enabled": false
+----
+

modules/develop/pages/managed-connectors/index.adoc

@@ -6,9 +6,7 @@
 Use Kafka Connect to integrate your Redpanda data with different
 data systems. As managed solutions, connectors offer a simpler way to integrate
 your data than manually creating a solution with the Kafka API. You can set up
-and manage these connectors for BYOC and Dedicated clusters in the Redpanda Cloud UI or Cloud API. Note that you remain responsible 
-for monitoring, alerting, and restarting Kafka Connect connectors, as these tasks 
-are not managed or monitored by Redpanda Support.
+and manage these connectors for BYOC and Dedicated clusters in the Redpanda Cloud UI or Cloud API. 
 
 include::shared:partial$kafka-connect.adoc[]
 
@@ -18,7 +16,7 @@ Each connector is either a source or a sink:
 The source connector's main task is to fetch data from these sources and convert 
 them into a format suitable for Redpanda.
 * A sink connector exports data from a Redpanda cluster and pushes it into a
-target system. Sink connectors read the data from Redpanda and transform it into 
+target system. Sink connectors read the data from Redpanda and transform it into
 a format that the target system can use.
 
 These sources and sinks work together to create a data pipeline that can move and transform data from one system to another.

modules/develop/pages/managed-connectors/monitor-connectors.adoc

@@ -1,6 +1,7 @@
-= Monitor Connectors
+= Monitor Kafka Connect
+:description: Use metrics to monitor the health of Kafka Connect.
 :page-aliases: deploy:deployment-option/cloud/managed-connectors/monitor-connectors.adoc
-:description: Use metrics to monitor the health of your Redpanda managed connectors.
+:description: Use metrics to monitor the health of Kafka Connect.
 
 include::shared:partial$kafka-connect.adoc[]
 

modules/get-started/pages/whats-new-cloud.adoc

@@ -27,7 +27,7 @@ xref:get-started:cluster-types/byoc/azure/create-byoc-cluster-azure.adoc[BYOC fo
 
 === Kafka Connect disabled on new clusters
 
-xref:develop:managed-connectors/index.adoc[Kafka Connect] is now disabled by default on all new clusters. To unlock this feature for your account, contact https://support.redpanda.com/hc/en-us/requests/new[Redpanda Support^]. Note that when Kafka Connect is enabled, there is a node running for Kafka Connect, even if connectors are not used.
+xref:develop:managed-connectors/index.adoc[Kafka Connect] is now disabled by default on all new clusters. To unlock this feature for your account, contact https://support.redpanda.com/hc/en-us/requests/new[Redpanda Support^]. If you previously enabled Kafka Connect on a cluster and want to xref:develop:managed-connectors/disable-kc.adoc[disable it], you can use the Cloud API.
 
 === Allowlist NAT gateway IP 
 

modules/security/pages/cloud-authentication.adoc

@@ -144,7 +144,7 @@ dynamic and short-lived credentials to interact with cloud provider APIs:
 * Data plane agent
 * Tiered Storage
 * Redpanda Console
-* Managed connectors
+* Kafka Connect
 
 xref:security:authorization/cloud-iam-policies.adoc[IAM policies] have constrained permissions so that each service can only
 access or manage its own data plane-scoped resources, following the principle of

modules/shared/partials/kafka-connect.adoc

@@ -1,5 +1,6 @@
 [IMPORTANT]
 ====
-- To unlock this feature for your account, contact https://support.redpanda.com/hc/en-us/requests/new[Redpanda Support^]. 
-- When Kafka Connect is enabled, there is a node running for Kafka Connect even if connectors are not used.
+- To enable this feature, contact https://support.redpanda.com/hc/en-us/requests/new[Redpanda Support^]. To disable this feature, see xref:develop:managed-connectors/disable-kc.adoc[].
+- Redpanda Support does not manage or monitor Kafka Connect. For fully-supported connectors, consider xref:develop:connect/about.adoc[Redpanda Connect].
+- When Kafka Connect is enabled, there is a dedicated node running even when no connectors are deployed.
 ====