DOC-783 Dedicated Limited availability (#139)

* Dedicated Limited availability

* Add secrets management reference

* review comments

* review comments

Author: asimms41

modules/develop/pages/connect/configuration/monitor-connect.adoc

@@ -1,7 +1,7 @@
-= Monitor Data Pipelines on BYOC Clusters
+= Monitor Data Pipelines on BYOC and Dedicated Clusters
 :description: Configure Prometheus monitoring of your data pipelines on BYOC clusters.
 
-You can configure monitoring on BYOC clusters to understand the behavior, health, and performance of your data pipelines. 
+You can configure monitoring on BYOC and Dedicated clusters to understand the behavior, health, and performance of your data pipelines. 
 
 Redpanda Connect automatically exports xref:components:metrics/about.adoc[detailed metrics for each component of your data pipeline] to a Prometheus endpoint, along with metrics for all other cluster services. You don’t need to update the configuration of your pipeline.
 

modules/develop/pages/connect/configuration/scale-pipelines.adoc

@@ -1,4 +1,4 @@
-= Scale Data Pipeline Resources on BYOC Clusters
+= Scale Data Pipeline Resources on BYOC and Dedicated Clusters
 :description: Learn how to manually scale resources for data pipelines using the Data Plane API.
 
 When you create a data pipeline through the Cloud UI, Redpanda Connect reserves compute resources for the exclusive use of that pipeline. This initial resource allocation is enough to experiment with pipelines that create low message volumes. 
@@ -16,7 +16,7 @@ Use the Cloud UI or Data Plane API to view resources already allocated to a data
 Cloud UI::
 +
 --
-. Log in to https://cloud.redpanda.com[Redpanda Cloud^].  
+. Log in to https://cloud.redpanda.com[Redpanda Cloud^].
 . Go to the cluster where the pipeline is set up.
 . On the **Connectors** page, select your pipeline and look at the value for **Resources**.
 +
@@ -47,7 +47,7 @@ This example allocates 1.2 vCPU and 500 MB of memory to a data pipeline. For `cp
 +
 [,bash]
 ----
-curl -X PUT "https://api-dfb1e463.crhjl9gj1v2u1117r1f0.byoc.prd.cloud.redpanda.com/v1alpha2/redpanda-connect/pipelines/xxx..."  \
+curl -X PUT "https://<data-plane-api-url>/v1alpha2/redpanda-connect/pipelines/xxx..."  \
  -H "Authorization: Bearer xxx..." \
  -H "accept: application/json" \
  -H "content-type: application/json" \

modules/develop/pages/connect/connect-quickstart.adoc

@@ -9,7 +9,7 @@ include::develop:partial$availability-message.adoc[]
 
 == Prerequisites
 
-A Redpanda Cloud account for Serverless or standard BYOC (not customer-managed VPC). If you don't already have an account, https://redpanda.com/try-redpanda/cloud-trial[sign up for a free trial^].
+A Redpanda Cloud account for Serverless, Dedicated or standard BYOC (not customer-managed VPC). If you don't already have an account, https://redpanda.com/try-redpanda/cloud-trial[sign up for a free trial^].
 
 == Before you start
 
@@ -40,17 +40,26 @@ BYOC::
 +
 Wait while your cluster is created.
 --
+Dedicated::
++
+--
+. Log in to https://cloud.redpanda.com[Redpanda Cloud^].
+. On the **Clusters** page, click **Create cluster**, then click **Create Dedicated cluster**.
+. On the **Cluster settings** page, enter **connect-quickstart** for the cluster name.
+. Select your cloud provider, then click **Next**.
+. On the **Networking** page, use the default **Public** connection type, and click **Create**.
++
+Wait while your cluster is created.
+--
 =====
 
 To complete your setup:
 
 . Go to the **Topics** page, click **Create topic** and enter **processed-emails** for the topic name. Use default values for the remaining properties and click **Create** and then **Close**.
-. Go to the **Security** page, and click **Create user**. Enter the username **connect**. Use the default values for the remaining properties. Remember to take a note of your password.
+. Go to the **Security** page, and click **Create user**. Enter the username **connect** and take a note of the password. You will need to use this later. Use the default values for the remaining properties.
 . Click **Create** and **Done**. 
 . Stay on the **Access control** page and click the **ACLs** tab.
 . Select the **connect** user you have just created. Click **Allow all operations** and then scroll down to click **OK**. 
-. Finally, go to the **Overview** page and click the **Kafka API** tab. 
-. Copy the bootstrap server URL into a text file. You will need it for the next steps.
 
 == Build your data pipeline
 
@@ -71,8 +80,7 @@ All Redpanda Connect configurations use a YAML file split into three sections:
 | A xref:components:outputs/kafka_franz.adoc[`kafka_franz` output] that writes messages to the **connect-output** topic on your cluster.
 |===
 
-. Go to the **Connectors** page on your cluster and click the **Redpanda Connect** tab.
-. Click **Create pipeline**.
+. Go to the **Connect** page on your cluster and click **Create pipeline**.
 . In **Pipeline name**, enter **emailprocessor-pipeline** and add a short description. For example, **Transforms email data using a mutation processor**.
 . In the **Configuration** box, paste the following configuration.
 
@@ -96,7 +104,7 @@ pipeline:
 output:
  kafka_franz:
    seed_brokers:
-     - <bootstrap-server-url>
+     - ${REDPANDA_BROKERS}
    sasl:
      - mechanism: SCRAM-SHA-256
        password: <cluster-password>
@@ -106,12 +114,9 @@ output:
      enabled: true
 ----
 
-
 +
-Replace the following placeholders:
-
-* `<bootstrap-server-url>`: The bootstrap server address you copied in <<before-you-start,Before you start>>.
-* `<cluster-password>`: The password of the connect user you set up in <<before-you-start,Before you start>>. 
+* Replace `<cluster-password>` with the password of the connect user you set up in <<before-you-start,Before you start>>. To avoid exposing secrets, Redpanda Connect also supports secret variables. For more information, see xref:develop:connect/configuration/secret-management.adoc[Manage Secrets].
+* `$\{REDPANDA_BROKERS}` is a contextual variable that references the bootstrap server address of your cluster. All Redpanda Cloud clusters automatically set this variable to the bootstrap server address so that you can add it to any of your pipelines.
 
 +
 NOTE: The Brave browser does not fully support code snippets. 
@@ -146,7 +151,7 @@ To see the pipeline output:
 
 To view the logs:
 
-. Return to the **Connectors** page on your cluster and select the **emailprocessor-pipeline**.
+. Return to the **Connect** page on your cluster and select the **emailprocessor-pipeline**.
 . Click the **Logs** tab and select each of the four log messages. You can see the sequence of events that start the data pipeline. For example, you can see when Redpanda Connect starts to write data to the topic:
 
 +
@@ -196,8 +201,7 @@ The snippet includes new configuration to:
 
 
 . Click **Update**.
-. After a few seconds, click **Stop**.
-. Click the **Logs** tab and select the most recent (final) log message. You can see the custom logging fields along with the uppercase user's name. 
+. Once the pipeline has started running, click the **Logs** tab and select the most recent (final) log message. You can see the custom logging fields along with the uppercase user's name. 
 
 +
 [source,json]
@@ -214,13 +218,14 @@ The snippet includes new configuration to:
     "time": "2024-08-22T17:33:46.676903284Z"
 }
 ----
+. Click **Stop**.
 
 == Clean up
 
 When you've finished experimenting with your data pipeline, you can delete the pipeline, topic, and cluster you created for this quickstart.
 
-. On the **Connectors** page, select your pipeline.
-. Click **Delete** and confirm your deletion to remove the data pipeline and associated logs.
+. On the **Connect** page, select the delete icon next to the **emailprocessor-pipeline**.
+. Confirm your deletion to remove the data pipeline and associated logs.
 . On the **Topics** page, delete the **processed-emails** topic.
 . Go back to the **Clusters** page and delete the **connect-quickstart** cluster. 
 

modules/develop/partials/availability-message.adoc

@@ -1,2 +1,2 @@
 NOTE: Redpanda Connect is currently in a limited availability (LA) release for  
-BYOC clusters. While it is also available as a beta feature for Serverless clusters, it is not suitable for production deployments.
+BYOC and Dedicated clusters. While it is also available as a beta feature for Serverless clusters, it is not suitable for production deployments.