Merge branch 'main' into DOC-1812-Document-Cloud-Feature-Schema-Registry-Contexts-Serverless-etc

Feediver1 · web-flow · commit ef8bcd3e0a52 · 2026-04-21T19:33:28.000-04:00
diff --git a/.github/workflows/check-playbook.yml b/.github/workflows/check-playbook.yml
@@ -0,0 +1,49 @@
+---
+name: Check playbook branches
+on:
+  pull_request:
+    paths:
+      - local-antora-playbook.yml
+  push:
+    branches: [main]
+    paths:
+      - local-antora-playbook.yml
+
+jobs:
+  check-branches:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+
+      - name: Check for non-standard branch references
+        run: |
+          # Allowed branch patterns in local-antora-playbook.yml.
+          # Any value not matching these is likely a PR branch that
+          # must be reverted before merge.
+          ALLOWED='main|HEAD|v/\*|shared|site-search|!v-end-of-life/\*'
+
+          # Extract all branch values from the playbook
+          BRANCHES=$(grep 'branches:' local-antora-playbook.yml \
+            | sed 's/.*branches:[[:space:]]*//' \
+            | tr -d "[]'" \
+            | tr ',' '\n' \
+            | sed 's/^[[:space:]]*//;s/[[:space:]]*$//')
+
+          FAILED=0
+          while IFS= read -r branch; do
+            [ -z "$branch" ] && continue
+            if ! echo "$branch" | grep -qE "^(${ALLOWED})$"; then
+              echo "::error::Non-standard branch reference found: '${branch}'"
+              FAILED=1
+            fi
+          done <<< "$BRANCHES"
+
+          if [ "$FAILED" -eq 1 ]; then
+            echo ""
+            echo "local-antora-playbook.yml contains non-standard branch references."
+            echo "These are used for cross-repo Netlify previews during PR development,"
+            echo "but must be reverted to standard values (e.g., 'main') before merging."
+            exit 1
+          fi
+
+          echo "Playbook OK: all branch references are standard."
diff --git a/modules/ROOT/nav.adoc b/modules/ROOT/nav.adoc
@@ -171,6 +171,7 @@
 
 *** xref:develop:connect/components/outputs/about.adoc[]
 **** xref:develop:connect/components/outputs/amqp_0_9.adoc[]
+**** xref:develop:connect/components/outputs/arc.adoc[]
 **** xref:develop:connect/components/outputs/aws_dynamodb.adoc[]
 **** xref:develop:connect/components/outputs/aws_kinesis.adoc[]
 **** xref:develop:connect/components/outputs/aws_kinesis_firehose.adoc[]
diff --git a/modules/develop/pages/connect/components/outputs/arc.adoc b/modules/develop/pages/connect/components/outputs/arc.adoc
@@ -0,0 +1,3 @@
+= arc
+:page-aliases: components:outputs/arc.adoc
+include::redpanda-connect:components:outputs/arc.adoc[tag=single-source]
diff --git a/modules/get-started/pages/cluster-types/byoc/aws/create-byoc-cluster-aws.adoc b/modules/get-started/pages/cluster-types/byoc/aws/create-byoc-cluster-aws.adoc
@@ -42,7 +42,7 @@ Optionally, click *Advanced settings* to specify up to five key-value custom tag
 ** For a xref:networking:cidr-ranges.adoc[CIDR range], choose one that does not overlap with your existing VPCs or your Redpanda network.
 ** Clusters with private networking include a setting for API Gateway network access. Public access exposes endpoints for Redpanda Console, the Data Plane API, and the MCP Server API, but they remain protected by your authentication and authorization controls. Private access restricts endpoint access to your VPC only.
 +
-NOTE: After the cluster is created, you can change the API Gateway access on the cluster settings page. If you change from public to private access, users without VPN access to the Redpanda VPC will lose access to these services.
+NOTE: After the cluster is created, you can change the API Gateway access on the Dataplane settings page. If you change from public to private access, users without VPN access to the Redpanda VPC will lose access to these services.
 . Click *Next*.
 . On the Deploy page, follow the steps to log in to Redpanda Cloud and deploy the agent.
 +
diff --git a/modules/get-started/pages/cluster-types/byoc/azure/create-byoc-cluster-azure.adoc b/modules/get-started/pages/cluster-types/byoc/azure/create-byoc-cluster-azure.adoc
@@ -168,7 +168,7 @@ Optionally, click *Advanced settings* to specify up to five key-value custom tag
 +
 Private access incurs an additional cost, since it involves deploying two network load balancers, instead of one. 
 +
-NOTE: After the cluster is created, you can change the API Gateway access on the cluster settings page. If you change from public to private access, users without VPN access to the Redpanda VPC will lose access to these services.
+NOTE: After the cluster is created, you can change the API Gateway access on the Dataplane settings page. If you change from public to private access, users without VPN access to the Redpanda VPC will lose access to these services.
 . Click *Next*.
 . On the Deploy page, follow the steps to log in to Redpanda Cloud and deploy the agent.
 +
diff --git a/modules/get-started/pages/cluster-types/byoc/gcp/create-byoc-cluster-gcp.adoc b/modules/get-started/pages/cluster-types/byoc/gcp/create-byoc-cluster-gcp.adoc
@@ -44,7 +44,7 @@ Optionally, click *Advanced settings* to specify up to five key-value custom GCP
 ** For a xref:networking:cidr-ranges.adoc[CIDR range], choose one that does not overlap with your existing VPCs or your Redpanda network.
 ** Clusters with private networking include a setting for API Gateway network access. Public access exposes endpoints for Redpanda Console, the Data Plane API, but they remain protected by your authentication and authorization controls. Private access restricts endpoint access to your VPC only.
 +
-NOTE: After the cluster is created, you can change the API Gateway access on the cluster settings page. If you change from public to private access, users without VPN access to the Redpanda VPC will lose access to these services.
+NOTE: After the cluster is created, you can change the API Gateway access on the Dataplane settings page. If you change from public to private access, users without VPN access to the Redpanda VPC will lose access to these services.
 . Click *Next*.
 . On the Deploy page, follow the steps to log in to Redpanda Cloud and deploy the agent.
 +
diff --git a/modules/get-started/pages/cluster-types/byoc/gcp/vpc-byo-gcp.adoc b/modules/get-started/pages/cluster-types/byoc/gcp/vpc-byo-gcp.adoc
@@ -738,7 +738,7 @@ You can delete the cluster in the Cloud UI.
 
 . Log in to https://cloud.redpanda.com[Redpanda Cloud^].
 . Select your cluster.
-. Go to the **Cluster settings** page and click **Delete**, then confirm your deletion. 
+. Go to the **Dataplane settings** page and click **Delete**, then confirm your deletion. 
 
 == Manage custom resource labels and network tags
 
diff --git a/modules/get-started/pages/cluster-types/create-dedicated-cloud-cluster.adoc b/modules/get-started/pages/cluster-types/create-dedicated-cloud-cluster.adoc
@@ -26,7 +26,7 @@ Private networks require either a VPC peering connection or a private connectivi
 +
 On Azure, private access incurs an additional cost, since it involves deploying two network load balancers, instead of one.
 +
-NOTE: After the cluster is created, you can change the API Gateway access on the cluster settings page. If you change from public to private access, users without VPN access to the Redpanda VPC will lose access to these services.
+NOTE: After the cluster is created, you can change the API Gateway access on the Dataplane settings page. If you change from public to private access, users without VPN access to the Redpanda VPC will lose access to these services.
 
 . Click *Create*.
 +
@@ -137,7 +137,7 @@ The message that you produced to the topic is displayed along with some other de
 
 If you don't want to continue experimenting with your cluster, you can delete it.
 
-Go to **Cluster settings** and click **Delete cluster**.
+Go to **Dataplane settings** and click **Delete cluster**.
 
 == Next steps
 
diff --git a/modules/get-started/pages/whats-new-cloud.adoc b/modules/get-started/pages/whats-new-cloud.adoc
@@ -22,6 +22,8 @@ Serverless clusters now support up to 100 Redpanda Connect pipelines and 100 MCP
 === Redpanda Connect updates
 
 * The Redpanda Connect pipeline creation and editing workflow has been simplified. The new UI replaces the previous multi-page wizard with a visual pipeline diagram, an IDE-like configuration editor, slash commands for inserting variables, and inline links to component documentation. See the xref:develop:connect/connect-quickstart.adoc[Redpanda Connect quickstart] to try it out.
+* Outputs:
+** xref:develop:connect/components/outputs/arc.adoc[arc]: Send data to an Arc columnar analytical database using its high-performance MessagePack ingestion endpoint.
 * Processors:
 ** xref:develop:connect/components/processors/string_split.adoc[string_split]: Splits strings into multiple parts using a delimiter, creating new messages or fields for each part.
 
@@ -147,11 +149,11 @@ Shadowing is supported on BYOC and Dedicated clusters running Redpanda version 2
 
 You can now view and export metrics from Serverless clusters to third-party monitoring systems like Prometheus and Grafana. See xref:manage:monitor-cloud.adoc[Monitor Redpanda Cloud] for details on configuring monitoring for your Serverless cluster and xref:reference:public-metrics-reference.adoc[Metrics Reference] for a list of metrics available in Serverless.
 
-=== User impersonation
+=== Account impersonation
 
-BYOC and Dedicated clusters now support unified authentication and authorization between the Redpanda Cloud UI and Redpanda with xref:security:cloud-authentication.adoc#user-impersonation[user impersonation]. This means you can authenticate to fine-grained access within Redpanda using the same credentials you use to authenticate to Redpanda Cloud. 
+BYOC and Dedicated clusters now support unified authentication and authorization between the Redpanda Cloud UI and Redpanda with xref:security:cloud-authentication.adoc#account-impersonation[account impersonation]. This means you can authenticate to fine-grained access within Redpanda using the same credentials you use to authenticate to Redpanda Cloud. 
 
-With user impersonation, the topics users see in the UI are identical to what they can access with the Cloud API or `rpk`, ensuring consistent permissions across all interfaces and clear auditing of data plane user actions.
+With account impersonation (originally called user impersonation), the topics users see in the UI are identical to what they can access with the Cloud API or `rpk`, ensuring consistent permissions across all interfaces and clear auditing of data plane user actions.
 
 === Redpanda Connect updates
 
@@ -211,7 +213,7 @@ BYOC and Dedicated clusters with private networking now allow control of API Gat
 * Public access exposes Redpanda Console, Data Plane API, and MCP Server API endpoints over the internet, although they remain protected by your authentication and authorization controls.
 * Private access restricts endpoint access to your private network (VPC or VNet) only.
 
-After the cluster is created, you can change the API Gateway access on the cluster settings page. If you change from public to private access, users without VPN access to the Redpanda VPC will lose access to these services.
+After the cluster is created, you can change the API Gateway access on the Dataplane settings page. If you change from public to private access, users without VPN access to the Redpanda VPC will lose access to these services.
 
 === Redpanda Connect updates
 
@@ -607,7 +609,7 @@ mTLS authentication is now available for Kafka API clients. You can xref:securit
 
 === Manage private connectivity in the UI
 
-You can now manage GCP Private Service Connect and AWS PrivateLink connections to your BYOC or Dedicated cluster on the *Cluster settings* page in Redpanda Cloud. See the steps for xref:networking:configure-privatelink-in-cloud-ui.adoc[PrivateLink] and xref:networking:configure-private-service-connect-in-cloud-ui.adoc[Private Service Connect].
+You can now manage GCP Private Service Connect and AWS PrivateLink connections to your BYOC or Dedicated cluster on the *Dataplane settings* page in Redpanda Cloud. See the steps for xref:networking:configure-privatelink-in-cloud-ui.adoc[PrivateLink] and xref:networking:configure-private-service-connect-in-cloud-ui.adoc[Private Service Connect].
 
 === Single message transforms
 
@@ -677,4 +679,4 @@ In the Redpanda Console UI, you can xref:manage:schema-reg/schema-reg-ui.adoc[pe
 
 === Maintenance windows
 
-With maintenance windows, you have greater flexibility to plan upgrades to your cluster. By default, Redpanda Cloud upgrades take place on Tuesdays. Optionally, on the **Cluster settings** page, you can select a window of specific off-hours for your business for Redpanda to apply updates. All times are in Coordinated Universal Time (UTC). Updates may start at any time during that window. 
+With maintenance windows, you have greater flexibility to plan upgrades to your cluster. By default, Redpanda Cloud upgrades take place on Tuesdays. Optionally, on the **Dataplane settings** page, you can select a window of specific off-hours for your business for Redpanda to apply updates. All times are in Coordinated Universal Time (UTC). Updates may start at any time during that window. 
diff --git a/modules/get-started/partials/quick-start-cloud.adoc b/modules/get-started/partials/quick-start-cloud.adoc
@@ -147,7 +147,7 @@ The message that you produced to the topic is displayed along with some other de
 
 If you don't want to continue experimenting with your cluster, you can delete it.
 
-Go to **Cluster settings** and click **Delete cluster**.
+Go to **Dataplane settings** and click **Delete cluster**.
 
 == Next steps
 
diff --git a/modules/manage/pages/maintenance.adoc b/modules/manage/pages/maintenance.adoc
@@ -9,7 +9,7 @@ Redpanda runs maintenance operations on clusters in a rolling fashion, accompani
 
 == Maintenance windows
 
-Redpanda Cloud may run maintenance operations on any day, at any time. You can override this default and schedule a specific maintenance window on your cluster's *Cluster settings* page. 
+Redpanda Cloud may run maintenance operations on any day, at any time. You can override this default and schedule a specific maintenance window on your cluster's *Dataplane settings* page. 
 
 If you select a *Scheduled* maintenance window, then Redpanda Cloud runs operations on the day and time specified. Maintenance windows typically take six hours. All operations begin during your maintenance window, but some operations may complete after the window closes. All times are in Coordinated Universal Time (UTC).
 
diff --git a/modules/networking/pages/configure-private-service-connect-in-cloud-ui.adoc b/modules/networking/pages/configure-private-service-connect-in-cloud-ui.adoc
@@ -31,7 +31,7 @@ Consider using Private Service Connect if you have multiple VPC networks and cou
 
 == Enable Private Service Connect for existing clusters
 
-. In the Redpanda Cloud UI, open your https://cloud.redpanda.com/clusters[cluster^], and click **Cluster settings**.
+. In the Redpanda Cloud UI, open your https://cloud.redpanda.com/clusters[cluster^], and click **Dataplane settings**.
 . Under Private Service Connect, click **Enable**. 
 ifdef::env-byoc[]
 . For xref:get-started:cluster-types/byoc/gcp/vpc-byo-gcp.adoc[BYOVPC clusters], you need a PSC NAT subnet with `purpose` set to `PRIVATE_SERVICE_CONNECT`. You also need to create VPC network firewall rules to allow Private Service Connect traffic. You can use the `gcloud` CLI:
@@ -71,10 +71,10 @@ Provide your values for the following placeholders:
 See the GCP documentation for https://cloud.google.com/vpc/docs/configure-private-service-connect-producer#add-subnet-psc[creating a subnet for Private Service Connect^]. 
 endif::[]
 . For the accepted consumers list, you need the GCP project IDs from which incoming connections will be accepted.
-. It may take several minutes for your cluster to update. When the update is complete, the Private Service Connect status in **Cluster settings** changes from **In progress** to **Enabled**.
+. It may take several minutes for your cluster to update. When the update is complete, the Private Service Connect status in **Dataplane settings** changes from **In progress** to **Enabled**.
 
 include::networking:partial$psc-ui.adoc[]
 
 == Disable Private Service Connect
 
-In **Cluster settings**, click **Disable**. Existing connections are closed after it is disabled. To connect using Private Service Connect again, you must re-enable it.
+In **Dataplane settings**, click **Disable**. Existing connections are closed after it is disabled. To connect using Private Service Connect again, you must re-enable it.
diff --git a/modules/networking/pages/configure-privatelink-in-cloud-ui.adoc b/modules/networking/pages/configure-privatelink-in-cloud-ui.adoc
@@ -29,12 +29,12 @@ include::networking:partial$dns_resolution.adoc[]
 
 == Enable endpoint service for existing clusters
 
-. In the Redpanda Cloud Console, select your https://cloud.redpanda.com/clusters[cluster^], and go to the *Cluster settings* page.
+. In the Redpanda Cloud Console, select your https://cloud.redpanda.com/clusters[cluster^], and go to the *Dataplane settings* page.
 . For AWS PrivateLink, click *Enable*.
 . On the Enable PrivateLink page, for Allowed principal ARNs, click *Add*, and enter the Amazon Resource Names (ARNs) for each AWS principal allowed to access the endpoint service. For example, for all principals in a specific account, use `arn:aws:iam::<account-id>:root`. See the AWS documentation on https://docs.aws.amazon.com/vpc/latest/privatelink/configure-endpoint-service.html#add-remove-permission[configuring an endpoint service^] for details.
 . Click *Add* after entering each ARN, and when finished, click *Enable*.
 . (Optional) To enable cross-region PrivateLink, add supported regions. See <<cross-region-privatelink>>.
-. It may take several minutes for your cluster to update. When the update is complete, the AWS PrivateLink status on the Cluster settings page changes from *In progress* to *Enabled*.
+. It may take several minutes for your cluster to update. When the update is complete, the AWS PrivateLink status on the Dataplane settings page changes from *In progress* to *Enabled*.
 
 NOTE: For help with issues when enabling PrivateLink, contact https://support.redpanda.com/hc/en-us/requests/new[Redpanda support^].
 
@@ -57,7 +57,7 @@ NOTE: Use `<cluster_domain>` as the domain you target with your DNS conditional
 
 === Get name of PrivateLink endpoint service
 
-You need the service name to <<create-vpc-endpoint,create a VPC endpoint>>. You can find the service name on the *Cluster settings* page after PrivateLink is enabled, or in the *How to Connect* section of the cluster overview.
+You need the service name to <<create-vpc-endpoint,create a VPC endpoint>>. You can find the service name on the *Dataplane settings* page after PrivateLink is enabled, or in the *How to Connect* section of the cluster overview.
 
 [,bash]
 ----
@@ -94,20 +94,20 @@ For more information about AWS cross-region PrivateLink support, see the https:/
 
 NOTE: The *Supported regions* option only appears in the UI for multi-AZ clusters.
 
-. In the Redpanda Cloud Console, select your https://cloud.redpanda.com/clusters[cluster^], and go to the cluster settings page.
+. In the Redpanda Cloud Console, select your https://cloud.redpanda.com/clusters[cluster^], and go to the Dataplane settings page.
 . In the AWS PrivateLink section, click *Edit* (or *Enable* if PrivateLink is not yet enabled).
 . In the *Supported regions* section, click *Add* to add a region from which PrivateLink endpoints can connect to your cluster.
 . Select an AWS region from the dropdown. The cluster's home region is automatically included and not shown in the list.
 . Repeat to add additional regions as needed.
 . Click *Save* (or *Enable*) to apply the changes.
 
-After saving, the *Supported regions* row on the cluster settings page displays your configured regions.
+After saving, the *Supported regions* row on the Dataplane settings page displays your configured regions.
 
 Clients in VPCs located in the supported regions can now create PrivateLink endpoints that connect to your Redpanda cluster.
 
 == Disable endpoint service
 
-On the Cluster settings page for the cluster, click *Disable* for PrivateLink. Existing connections are closed after the AWS PrivateLink service is disabled. To connect using PrivateLink again, you must re-enable the service.
+On the Dataplane settings page for the cluster, click *Disable* for PrivateLink. Existing connections are closed after the AWS PrivateLink service is disabled. To connect using PrivateLink again, you must re-enable the service.
 
 include::shared:partial$suggested-reading.adoc[]
 
diff --git a/modules/networking/pages/dedicated/gcp/configure-psc-in-ui.adoc b/modules/networking/pages/dedicated/gcp/configure-psc-in-ui.adoc
diff --git a/modules/networking/pages/serverless/aws/privatelink-ui.adoc b/modules/networking/pages/serverless/aws/privatelink-ui.adoc
diff --git a/modules/networking/partials/psc-ui.adoc b/modules/networking/partials/psc-ui.adoc
diff --git a/modules/security/pages/authorization/rbac/rbac.adoc b/modules/security/pages/authorization/rbac/rbac.adoc
diff --git a/modules/security/pages/cloud-authentication.adoc b/modules/security/pages/cloud-authentication.adoc
diff --git a/modules/security/partials/predefined-roles.adoc b/modules/security/partials/predefined-roles.adoc

Original file line number	Diff line number	Diff line change
`@@ -0,0 +1,3 @@`
	`1`	`+= arc`
	`2`	`+:page-aliases: components:outputs/arc.adoc`
	`3`	`+include::redpanda-connect:components:outputs/arc.adoc[tag=single-source]`
Original file line number	Diff line number	Diff line change
`@@ -42,7 +42,7 @@ Optionally, click Advanced settings to specify up to five key-value custom tag`
`42`	`42`	`** For a xref:networking:cidr-ranges.adoc[CIDR range], choose one that does not overlap with your existing VPCs or your Redpanda network.`
`43`	`43`	`** Clusters with private networking include a setting for API Gateway network access. Public access exposes endpoints for Redpanda Console, the Data Plane API, and the MCP Server API, but they remain protected by your authentication and authorization controls. Private access restricts endpoint access to your VPC only.`
`44`	`44`	`+`
`45`		`-NOTE: After the cluster is created, you can change the API Gateway access on the cluster settings page. If you change from public to private access, users without VPN access to the Redpanda VPC will lose access to these services.`
	`45`	`+NOTE: After the cluster is created, you can change the API Gateway access on the Dataplane settings page. If you change from public to private access, users without VPN access to the Redpanda VPC will lose access to these services.`
`46`	`46`	`. Click Next.`
`47`	`47`	`. On the Deploy page, follow the steps to log in to Redpanda Cloud and deploy the agent.`
`48`	`48`	`+`
Original file line number	Diff line number	Diff line change
`@@ -168,7 +168,7 @@ Optionally, click Advanced settings to specify up to five key-value custom tag`
`168`	`168`	`+`
`169`	`169`	`Private access incurs an additional cost, since it involves deploying two network load balancers, instead of one.`
`170`	`170`	`+`
`171`		`-NOTE: After the cluster is created, you can change the API Gateway access on the cluster settings page. If you change from public to private access, users without VPN access to the Redpanda VPC will lose access to these services.`
	`171`	`+NOTE: After the cluster is created, you can change the API Gateway access on the Dataplane settings page. If you change from public to private access, users without VPN access to the Redpanda VPC will lose access to these services.`
`172`	`172`	`. Click Next.`
`173`	`173`	`. On the Deploy page, follow the steps to log in to Redpanda Cloud and deploy the agent.`
`174`	`174`	`+`
Original file line number	Diff line number	Diff line change
`@@ -44,7 +44,7 @@ Optionally, click Advanced settings to specify up to five key-value custom GCP`
`44`	`44`	`** For a xref:networking:cidr-ranges.adoc[CIDR range], choose one that does not overlap with your existing VPCs or your Redpanda network.`
`45`	`45`	`** Clusters with private networking include a setting for API Gateway network access. Public access exposes endpoints for Redpanda Console, the Data Plane API, but they remain protected by your authentication and authorization controls. Private access restricts endpoint access to your VPC only.`
`46`	`46`	`+`
`47`		`-NOTE: After the cluster is created, you can change the API Gateway access on the cluster settings page. If you change from public to private access, users without VPN access to the Redpanda VPC will lose access to these services.`
	`47`	`+NOTE: After the cluster is created, you can change the API Gateway access on the Dataplane settings page. If you change from public to private access, users without VPN access to the Redpanda VPC will lose access to these services.`
`48`	`48`	`. Click Next.`
`49`	`49`	`. On the Deploy page, follow the steps to log in to Redpanda Cloud and deploy the agent.`
`50`	`50`	`+`
Original file line number	Diff line number	Diff line change
`@@ -26,7 +26,7 @@ Private networks require either a VPC peering connection or a private connectivi`
`26`	`26`	`+`
`27`	`27`	`On Azure, private access incurs an additional cost, since it involves deploying two network load balancers, instead of one.`
`28`	`28`	`+`
`29`		`-NOTE: After the cluster is created, you can change the API Gateway access on the cluster settings page. If you change from public to private access, users without VPN access to the Redpanda VPC will lose access to these services.`
	`29`	`+NOTE: After the cluster is created, you can change the API Gateway access on the Dataplane settings page. If you change from public to private access, users without VPN access to the Redpanda VPC will lose access to these services.`
`30`	`30`
`31`	`31`	`. Click Create.`
`32`	`32`	`+`
`@@ -137,7 +137,7 @@ The message that you produced to the topic is displayed along with some other de`
`137`	`137`
`138`	`138`	`If you don't want to continue experimenting with your cluster, you can delete it.`
`139`	`139`
`140`		`-Go to Cluster settings and click Delete cluster.`
	`140`	`+Go to Dataplane settings and click Delete cluster.`
`141`	`141`
`142`	`142`	`== Next steps`
`143`	`143`