From 282be2cc31e593b904605a7af00863c021686b8f Mon Sep 17 00:00:00 2001 From: Joyce Fee Date: Wed, 4 Feb 2026 10:20:30 -0500 Subject: [PATCH 01/20] Add SQL Engine workshop documentation for BYOC Add comprehensive workshop guide for provisioning and using Redpanda SQL Engine (Oxla) with BYOC clusters. The workshop covers: - Overview of SQL Engine architecture and capabilities - Limitations and prerequisites - BYOC cluster provisioning with SQL Engine - User management and authentication - Creating tables from Redpanda topics with Schema Registry integration - Installing and using psql client - Scaling operations via Fleet Management API - Cluster deletion procedures Organized for a 2-3 hour hands-on workshop with practical examples. Co-Authored-By: Claude Sonnet 4.5 --- modules/ROOT/nav.adoc | 2 + modules/manage/pages/sql-engine/workshop.adoc | 443 ++++++++++++++++++ 2 files changed, 445 insertions(+) create mode 100644 modules/manage/pages/sql-engine/workshop.adoc diff --git a/modules/ROOT/nav.adoc b/modules/ROOT/nav.adoc index 4380ada99..a6917f350 100644 --- a/modules/ROOT/nav.adoc +++ b/modules/ROOT/nav.adoc @@ -23,6 +23,8 @@ *** xref:get-started:cluster-types/byoc/remote-read-replicas.adoc[] ** xref:get-started:cluster-types/create-dedicated-cloud-cluster.adoc[] +* xref:manage:sql-engine/workshop.adoc[Redpanda SQL Engine] + * xref:ai-agents:index.adoc[Agentic AI] ** xref:ai-agents:mcp/index.adoc[MCP] *** xref:ai-agents:mcp/overview.adoc[MCP Overview] diff --git a/modules/manage/pages/sql-engine/workshop.adoc b/modules/manage/pages/sql-engine/workshop.adoc new file mode 100644 index 000000000..169161230 --- /dev/null +++ b/modules/manage/pages/sql-engine/workshop.adoc @@ -0,0 +1,443 @@ += Redpanda SQL Engine Workshop +:description: Learn how to provision, configure, and use Redpanda SQL Engine (Oxla) with BYOC clusters to query streaming data using SQL. +:page-categories: Cloud, SQL, BYOC + +This workshop guides you through provisioning and using Redpanda SQL Engine (formerly Oxla) in a Bring Your Own Cloud (BYOC) environment. You'll learn to query Redpanda topics using standard SQL, manage users and permissions, and scale your SQL Engine deployment. + +== What is Redpanda SQL Engine? + +Redpanda SQL Engine is a SQL query engine that runs alongside your Redpanda cluster, allowing you to query streaming data using familiar SQL syntax instead of building custom consumers or streaming applications. It transforms your Redpanda cluster into a SQL-addressable analytics surface, making it easier to explore, analyze, and join streaming data with minimal integration overhead. + +From an architecture perspective, SQL Engine runs as its own cluster with a configurable number of replicas. It can be fronted by either an internal or external load balancer, allowing you to restrict access to in-cluster components (like Redpanda Connect) or expose it more broadly to applications within your VPC or to public clients. + +SQL Engine integrates directly with Redpanda Schema Registry to automatically derive table schemas from your topics. This means you can immediately query topics containing Protobuf data without manually defining schemas. The engine supports standard SQL operations including JOINs, aggregations, window functions, and complex analytical queries. + +In Redpanda Cloud BYOC deployments, SQL Engine is deployed as an additional service inside your Redpanda data plane. It's controlled via the `redpanda_oxla` section of your cluster specification and can be enabled per cluster using Fleet Management API operations. + +== Limitations + +SQL Engine has the following limitations in its current release: + +* **Read-only access:** You cannot write to Redpanda-backed tables using `INSERT`, `UPDATE`, or `DELETE` statements +* **Protobuf only:** Tables can only be created from Redpanda topics that use Protobuf serialization with schemas stored in Schema Registry +* **Schema Registry required:** Table schemas must be derived from Redpanda Schema Registry; manual schema definition is not supported +* **Backward-compatible schemas only:** Schema evolution must be backward-compatible; breaking schema changes may cause query failures +* **Flat structures only:** The first release supports only the `FLATTEN` struct mapping policy; compound types, variants, and JSON mapping are not yet supported +* **Single-dimensional arrays:** Arrays of arrays and nested complex types are not supported +* **No streaming queries:** Queries execute in on-demand mode and return results when complete; continuous streaming queries are not supported +* **Limited type support:** Some Redpanda data types are not supported: +** UUID +** Fixed-length binary types +** Map types +** Variant types (coming in future release) +** Geometry and geography types (limited support) +* **No consumer groups:** SQL Engine does not use Kafka consumer groups; partition assignment is handled by the query planner + +== Prerequisites + +Before creating a BYOC cluster with SQL Engine: + +* Access to Redpanda Cloud and a resource group that will own the BYOC cluster +* The `enable-redpanda-oxla` feature flag enabled for your resource group in LaunchDarkly +* Decision on network exposure mode: +** Cluster-internal only (no load balancer) +** Internal load balancer (VPC/peered VPC access) +** External load balancer (publicly accessible endpoint) + +== How to provision SQL Engine using Redpanda BYOC + +Provisioning a BYOC cluster with SQL Engine follows the standard BYOC workflow. The only differences are enabling the SQL Engine feature flag for your resource group and optionally configuring network exposure. + +=== Create the BYOC cluster + +Follow the standard BYOC cluster creation process: + +. In the Redpanda Cloud UI, navigate to your Oxla-enabled resource group +. Click *Create Cluster* and select *BYOC* +. Choose your cloud provider (AWS, GCP, or Azure) and region +. Configure networking details (VPC/VNet, CIDR ranges) +. Download the Terraform bundle generated by the wizard +. Extract the bundle locally and run the bootstrap script: ++ +[,bash] +---- +cd +./bootstrap.sh +---- + +. Wait for the cluster to become Ready in the Redpanda Cloud UI + +When the cluster provisions, SQL Engine is automatically deployed into the same data plane because the resource group has the `enable-redpanda-oxla` feature flag enabled. + +=== Configure SQL Engine network exposure + +By default, SQL Engine deploys with cluster-internal access only. To change the network exposure mode, use the Fleet Management API. + +**Enable with internal load balancer (VPC access):** + +[,bash] +---- +fleetmgmt operation create --type update \ + --update-paths 'spec.redpanda_oxla' \ + --redpanda-proto '{"spec": {"redpanda_oxla": {"enabled": true, "replicas": 1, "load_balancer": {"enabled": true, "type": 1}}}}' \ + --cluster-ids +---- + +**Enable with external load balancer (public access):** + +[,bash] +---- +fleetmgmt operation create --type update \ + --update-paths 'spec.redpanda_oxla' \ + --redpanda-proto '{"spec": {"redpanda_oxla": {"enabled": true, "replicas": 1, "load_balancer": {"enabled": true, "type": 2}}}}' \ + --cluster-ids +---- + +After enabling an external load balancer, manually run the appropriate Terraform apply for the infrastructure module on the agent VM. + +== Manage SQL Engine + +SQL Engine uses PostgreSQL-compatible authentication and authorization. You manage users, roles, and privileges using standard SQL commands. + +=== Retrieve the superuser password + +SQL Engine creates a superuser account during provisioning. Retrieve the password from the Kubernetes secret: + +[,bash] +---- +kubectl get secret -n redpanda-oxla oxla-superuser -o jsonpath='{.data.password}' | base64 -d +---- + +=== Create users + +Connect to SQL Engine and create users with the `CREATE ROLE` statement: + +[,sql] +---- +CREATE ROLE data_analyst WITH LOGIN PASSWORD 'secure_password'; +---- + +=== Grant privileges + +Grant specific privileges to users or roles: + +[,sql] +---- +-- Grant table read access +GRANT SELECT ON TABLE customer_events TO data_analyst; + +-- Grant schema-level access +GRANT USAGE ON SCHEMA public TO data_analyst; + +-- Grant all privileges on a table +GRANT ALL PRIVILEGES ON TABLE order_events TO data_analyst; +---- + +=== Authorization and authentication + +SQL Engine implements PostgreSQL-compatible role-based access control (RBAC): + +**Authentication:** Users authenticate using username and password over PostgreSQL wire protocol. SQL Engine supports standard PostgreSQL authentication methods including SCRAM-SHA-256. + +**Authorization:** Privileges control what users can do: + +* `SELECT` - Read data from tables +* `INSERT` - Write data to tables (not supported for Redpanda-backed tables) +* `UPDATE` - Modify existing data (not supported for Redpanda-backed tables) +* `DELETE` - Remove data (not supported for Redpanda-backed tables) +* `USAGE` - Access schemas and other objects +* `CREATE` - Create new objects (tables, connections, sources) + +Use `GRANT` and `REVOKE` statements to manage access control. + +== Create tables + +SQL Engine allows you to create tables backed by Redpanda topics. Tables are read-only and automatically derive their schema from Redpanda Schema Registry. + +=== Create a connection to Redpanda + +First, define a connection to your Redpanda cluster: + +[,sql] +---- +CREATE KAFKA CONNECTION redpanda_prod +OPTIONS ( + 'initial_brokers' 'broker-1:9092,broker-2:9092,broker-3:9092', + 'schema_registry_url' 'http://schema-registry:8081', + 'sasl_mechanism' 'SCRAM-SHA-256', + 'sasl_user' 'sql-engine-user', + 'sasl_password' 'your-password' +); +---- + +For mTLS authentication: + +[,sql] +---- +CREATE KAFKA CONNECTION redpanda_mtls +OPTIONS ( + 'initial_brokers' 'broker-1:9092,broker-2:9092,broker-3:9092', + 'schema_registry_url' 'https://schema-registry:8081', + 'truststore' '', + 'key_store_key' '', + 'key_store_cert' '' +); +---- + +=== Create a table from a Redpanda topic + +Create a queryable table from a Redpanda topic: + +[,sql] +---- +CREATE KAFKA SOURCE customer_events +TOPIC customer_events_topic +CONNECTION redpanda_prod; +---- + +With optional parameters: + +[,sql] +---- +CREATE KAFKA SOURCE order_events +TOPIC orders +SCHEMA_SUBJECT orders-value +SCHEMA_LOOKUP_POLICY LATEST +ERROR_HANDLING_POLICY FILL_NULL +CONNECTION redpanda_prod; +---- + +**Parameters:** + +* `TOPIC` - Name of the Redpanda topic +* `SCHEMA_SUBJECT` - Schema Registry subject name (optional, defaults to TopicNameStrategy) +* `SCHEMA_LOOKUP_POLICY` - How to look up record schemas: +** `LATEST` - Use the latest schema from Schema Registry (default) +** `SCHEMA_ID` - Use the schema ID prefixed in each record +* `ERROR_HANDLING_POLICY` - How to handle deserialization failures: +** `FAIL` - Fail the query (default) +** `FILL_NULL` - Fill columns with NULL values +** `DROP_RECORD` - Skip the record +* `CONNECTION` - Connection name to use + +=== Query the table + +Query Redpanda-backed tables using standard SQL: + +[,sql] +---- +-- Simple query +SELECT customer_id, event_type, timestamp +FROM customer_events +WHERE event_type = 'purchase' +LIMIT 100; + +-- Aggregation +SELECT event_type, COUNT(*) as event_count +FROM customer_events +GROUP BY event_type; + +-- Join with another table +SELECT + c.customer_id, + c.event_type, + o.order_total +FROM customer_events c +JOIN order_events o ON c.customer_id = o.customer_id +WHERE c.timestamp > NOW() - INTERVAL '1 day'; +---- + +=== Metadata columns + +All Redpanda-backed tables include metadata columns: + +* `redpanda.partition` - Partition ID +* `redpanda.offset` - Record offset +* `redpanda.timestamp` - Record timestamp +* `redpanda.timestamp_source` - Timestamp source (broker or producer) +* `redpanda.headers` - Message headers +* `redpanda.key` - Raw key (populated on deserialization error with FILL_NULL policy) +* `redpanda.value` - Raw value (populated on deserialization error with FILL_NULL policy) + +Query metadata columns like any other column: + +[,sql] +---- +SELECT + customer_id, + event_type, + redpanda.partition, + redpanda.offset, + redpanda.timestamp +FROM customer_events; +---- + +== Install SQL Engine client tools + +To query SQL Engine, use any PostgreSQL-compatible client. This section shows how to use `psql`, the standard PostgreSQL command-line client. + +=== Install psql + +**On macOS:** + +[,bash] +---- +brew install postgresql +---- + +**On Ubuntu/Debian:** + +[,bash] +---- +sudo apt-get update +sudo apt-get install postgresql-client +---- + +**On RHEL/CentOS:** + +[,bash] +---- +sudo yum install postgresql +---- + +=== Get the SQL Engine endpoint + +Retrieve the SQL Engine connection endpoint based on your load balancer configuration. + +**For internal load balancer:** + +[,bash] +---- +kubectl get svc -n redpanda-oxla oxla-lb -o jsonpath='{.status.loadBalancer.ingress[0].hostname}' +---- + +**For external load balancer:** + +[,bash] +---- +kubectl get svc -n redpanda-oxla oxla-external-lb -o jsonpath='{.status.loadBalancer.ingress[0].hostname}' +---- + +**For cluster-internal (no load balancer):** + +[,bash] +---- +kubectl get svc -n redpanda-oxla oxla -o jsonpath='{.spec.clusterIP}' +---- + +=== Connect with psql + +Connect to SQL Engine using the superuser credentials: + +[,bash] +---- +psql -h -p 5432 -U oxla_admin -d oxla +---- + +Enter the superuser password when prompted. + +=== Run queries + +Once connected, you can run SQL queries: + +[,sql] +---- +-- List all tables +\dt + +-- Describe a table +\d customer_events + +-- Run a query +SELECT * FROM customer_events LIMIT 10; + +-- Exit psql +\q +---- + +== Scale up or down using Data Plane APIs + +You can scale SQL Engine by adjusting the number of replicas using Fleet Management operations. + +=== Scale up + +Increase the number of SQL Engine replicas to handle higher query loads: + +[,bash] +---- +fleetmgmt operation create --type update \ + --update-paths 'spec.redpanda_oxla.replicas' \ + --redpanda-proto '{"spec": {"redpanda_oxla": {"replicas": 3}}}' \ + --cluster-ids +---- + +=== Scale down + +Decrease the number of replicas to reduce resource usage: + +[,bash] +---- +fleetmgmt operation create --type update \ + --update-paths 'spec.redpanda_oxla.replicas' \ + --redpanda-proto '{"spec": {"redpanda_oxla": {"replicas": 1}}}' \ + --cluster-ids +---- + +=== Verify scaling operation + +Check the operation status: + +[,bash] +---- +fleetmgmt operation get +---- + +Verify the new replica count: + +[,bash] +---- +kubectl get pods -n redpanda-oxla +---- + +== Delete or destroy the cluster + +To remove SQL Engine from your cluster or delete the entire BYOC cluster, use Fleet Management operations. + +=== Disable SQL Engine only + +To remove SQL Engine while keeping the Redpanda cluster running: + +[,bash] +---- +fleetmgmt operation create --type update \ + --update-paths 'spec.redpanda_oxla.enabled' \ + --redpanda-proto '{"spec": {"redpanda_oxla": {"enabled": false}}}' \ + --cluster-ids +---- + +This stops all SQL Engine pods and removes the service from your data plane. + +=== Delete the entire BYOC cluster + +To delete the BYOC cluster including SQL Engine: + +. In the Redpanda Cloud UI, navigate to the cluster details page +. Click *Delete Cluster* +. Confirm the deletion +. Run the Terraform destroy command from your BYOC bundle directory: ++ +[,bash] +---- +cd +terraform destroy +---- + +. Confirm the destruction when prompted + +This removes all Redpanda and SQL Engine resources from your cloud account. + +== Next steps + +* Explore the https://docs.oxla.com/welcome[SQL Engine documentation^] for detailed SQL syntax and function references +* Review xref:manage:schema-reg/schema-reg-overview.adoc[] for managing Protobuf schemas +* Learn about xref:get-started:cluster-types/byoc/index.adoc[] deployment options From dcbb0cf339a1d66851fbbcd713bf77642bd8110d Mon Sep 17 00:00:00 2001 From: Joyce Fee Date: Wed, 4 Feb 2026 11:22:47 -0500 Subject: [PATCH 02/20] Convert Limitations section to table format --- modules/manage/pages/sql-engine/workshop.adoc | 51 ++++++++++++++----- 1 file changed, 37 insertions(+), 14 deletions(-) diff --git a/modules/manage/pages/sql-engine/workshop.adoc b/modules/manage/pages/sql-engine/workshop.adoc index 169161230..8fe321bc4 100644 --- a/modules/manage/pages/sql-engine/workshop.adoc +++ b/modules/manage/pages/sql-engine/workshop.adoc @@ -18,20 +18,43 @@ In Redpanda Cloud BYOC deployments, SQL Engine is deployed as an additional serv SQL Engine has the following limitations in its current release: -* **Read-only access:** You cannot write to Redpanda-backed tables using `INSERT`, `UPDATE`, or `DELETE` statements -* **Protobuf only:** Tables can only be created from Redpanda topics that use Protobuf serialization with schemas stored in Schema Registry -* **Schema Registry required:** Table schemas must be derived from Redpanda Schema Registry; manual schema definition is not supported -* **Backward-compatible schemas only:** Schema evolution must be backward-compatible; breaking schema changes may cause query failures -* **Flat structures only:** The first release supports only the `FLATTEN` struct mapping policy; compound types, variants, and JSON mapping are not yet supported -* **Single-dimensional arrays:** Arrays of arrays and nested complex types are not supported -* **No streaming queries:** Queries execute in on-demand mode and return results when complete; continuous streaming queries are not supported -* **Limited type support:** Some Redpanda data types are not supported: -** UUID -** Fixed-length binary types -** Map types -** Variant types (coming in future release) -** Geometry and geography types (limited support) -* **No consumer groups:** SQL Engine does not use Kafka consumer groups; partition assignment is handled by the query planner +[cols="1,3"] +|=== +| Limitation | Description + +| Read-only access +| You cannot write to Redpanda-backed tables using `INSERT`, `UPDATE`, or `DELETE` statements + +| Protobuf only +| Tables can only be created from Redpanda topics that use Protobuf serialization with schemas stored in Schema Registry + +| Schema Registry required +| Table schemas must be derived from Redpanda Schema Registry; manual schema definition is not supported + +| Backward-compatible schemas only +| Schema evolution must be backward-compatible; breaking schema changes may cause query failures + +| Flat structures only +| The first release supports only the `FLATTEN` struct mapping policy; compound types, variants, and JSON mapping are not yet supported + +| Single-dimensional arrays +| Arrays of arrays and nested complex types are not supported + +| No streaming queries +| Queries execute in on-demand mode and return results when complete; continuous streaming queries are not supported + +| Limited type support +a| Some Redpanda data types are not supported: + +* UUID +* Fixed-length binary types +* Map types +* Variant types (coming in future release) +* Geometry and geography types (limited support) + +| No consumer groups +| SQL Engine does not use Kafka consumer groups; partition assignment is handled by the query planner +|=== == Prerequisites From 2a36d59e9dd212e5c9b6999b420d2bca25a5608e Mon Sep 17 00:00:00 2001 From: Joyce Fee <102751339+Feediver1@users.noreply.github.com> Date: Wed, 4 Feb 2026 10:37:18 -0600 Subject: [PATCH 03/20] Apply suggestions from code review Joyce edits --- modules/manage/pages/sql-engine/workshop.adoc | 50 +++++++++---------- 1 file changed, 25 insertions(+), 25 deletions(-) diff --git a/modules/manage/pages/sql-engine/workshop.adoc b/modules/manage/pages/sql-engine/workshop.adoc index 8fe321bc4..dbd19f603 100644 --- a/modules/manage/pages/sql-engine/workshop.adoc +++ b/modules/manage/pages/sql-engine/workshop.adoc @@ -16,7 +16,7 @@ In Redpanda Cloud BYOC deployments, SQL Engine is deployed as an additional serv == Limitations -SQL Engine has the following limitations in its current release: +SQL Engine has the following limitations in its current state: [cols="1,3"] |=== @@ -58,28 +58,28 @@ a| Some Redpanda data types are not supported: == Prerequisites -Before creating a BYOC cluster with SQL Engine: +Before creating a BYOC cluster with SQL Engine you must: -* Access to Redpanda Cloud and a resource group that will own the BYOC cluster -* The `enable-redpanda-oxla` feature flag enabled for your resource group in LaunchDarkly -* Decision on network exposure mode: +* Have access to Redpanda Cloud and a resource group that will own the BYOC cluster +* Enable (`enable-redpanda-oxla`) the feature flag for your resource group in LaunchDarkly +* Decide on the level of network exposure mode: ** Cluster-internal only (no load balancer) ** Internal load balancer (VPC/peered VPC access) ** External load balancer (publicly accessible endpoint) -== How to provision SQL Engine using Redpanda BYOC +== Provision Redpanda SQL Engine using BYOC -Provisioning a BYOC cluster with SQL Engine follows the standard BYOC workflow. The only differences are enabling the SQL Engine feature flag for your resource group and optionally configuring network exposure. +Provisioning a BYOC cluster with Redpanda SQL Engine follows the standard BYOC workflow. The only differences are that you must enable the SQL Engine feature flag for your resource group and, optionally, configuring network exposure. === Create the BYOC cluster Follow the standard BYOC cluster creation process: -. In the Redpanda Cloud UI, navigate to your Oxla-enabled resource group -. Click *Create Cluster* and select *BYOC* -. Choose your cloud provider (AWS, GCP, or Azure) and region -. Configure networking details (VPC/VNet, CIDR ranges) -. Download the Terraform bundle generated by the wizard +. In the Redpanda Cloud UI, navigate to your Oxla-enabled resource group. +. Click *Create Cluster* and select *BYOC*. +. Choose your cloud provider (AWS, GCP, or Azure) and region. +. Configure networking details (VPC/VNet, CIDR ranges). +. Download the Terraform bundle generated by the wizard. . Extract the bundle locally and run the bootstrap script: + [,bash] @@ -88,15 +88,15 @@ cd ./bootstrap.sh ---- -. Wait for the cluster to become Ready in the Redpanda Cloud UI +. Wait for the cluster to reflect the Ready state in the Redpanda Cloud UI. -When the cluster provisions, SQL Engine is automatically deployed into the same data plane because the resource group has the `enable-redpanda-oxla` feature flag enabled. +When the cluster provisions, Redpanda SQL Engine is automatically deployed into the same data plane because the resource group has the `enable-redpanda-oxla` feature flag enabled. -=== Configure SQL Engine network exposure +=== Configure Redpanda SQL Engine network exposure -By default, SQL Engine deploys with cluster-internal access only. To change the network exposure mode, use the Fleet Management API. +By default, Redpanda SQL Engine deploys with cluster-internal access only. To change the network exposure mode, use the Fleet Management API. -**Enable with internal load balancer (VPC access):** +**To enable with internal load balancer (VPC access): [,bash] ---- @@ -106,7 +106,7 @@ fleetmgmt operation create --type update \ --cluster-ids ---- -**Enable with external load balancer (public access):** +To enable with external load balancer (public access): [,bash] ---- @@ -118,13 +118,13 @@ fleetmgmt operation create --type update \ After enabling an external load balancer, manually run the appropriate Terraform apply for the infrastructure module on the agent VM. -== Manage SQL Engine +== Manage Redpanda SQL Engine -SQL Engine uses PostgreSQL-compatible authentication and authorization. You manage users, roles, and privileges using standard SQL commands. +Redpanda SQL Engine uses PostgreSQL-compatible authentication and authorization. You manage users, roles, and privileges using standard SQL commands. === Retrieve the superuser password -SQL Engine creates a superuser account during provisioning. Retrieve the password from the Kubernetes secret: +Redpanda SQL Engine creates a superuser account during provisioning. Retrieve the password from the Kubernetes secret: [,bash] ---- @@ -133,7 +133,7 @@ kubectl get secret -n redpanda-oxla oxla-superuser -o jsonpath='{.data.password} === Create users -Connect to SQL Engine and create users with the `CREATE ROLE` statement: +Connect to Redpanda SQL Engine and create users with the `CREATE ROLE` statement: [,sql] ---- @@ -158,9 +158,9 @@ GRANT ALL PRIVILEGES ON TABLE order_events TO data_analyst; === Authorization and authentication -SQL Engine implements PostgreSQL-compatible role-based access control (RBAC): +Redpanda SQL Engine implements PostgreSQL-compatible role-based access control (RBAC): -**Authentication:** Users authenticate using username and password over PostgreSQL wire protocol. SQL Engine supports standard PostgreSQL authentication methods including SCRAM-SHA-256. +**Authentication:** Users authenticate using username and password over PostgreSQL wire protocol. Redpanda SQL Engine supports standard PostgreSQL authentication methods including SCRAM-SHA-256. **Authorization:** Privileges control what users can do: @@ -175,7 +175,7 @@ Use `GRANT` and `REVOKE` statements to manage access control. == Create tables -SQL Engine allows you to create tables backed by Redpanda topics. Tables are read-only and automatically derive their schema from Redpanda Schema Registry. +Redpanda SQL Engine allows you to create tables backed by Redpanda topics. Tables are read-only and automatically derive their schema from Redpanda Schema Registry. === Create a connection to Redpanda From 52afdad06f1df13db2a31908497623ad5a4eb2ae Mon Sep 17 00:00:00 2001 From: Joyce Fee Date: Wed, 4 Feb 2026 11:48:03 -0500 Subject: [PATCH 04/20] Convert Parameters section to table format --- modules/manage/pages/sql-engine/workshop.adoc | 38 +++++++++++++------ 1 file changed, 26 insertions(+), 12 deletions(-) diff --git a/modules/manage/pages/sql-engine/workshop.adoc b/modules/manage/pages/sql-engine/workshop.adoc index dbd19f603..337580e99 100644 --- a/modules/manage/pages/sql-engine/workshop.adoc +++ b/modules/manage/pages/sql-engine/workshop.adoc @@ -230,18 +230,32 @@ ERROR_HANDLING_POLICY FILL_NULL CONNECTION redpanda_prod; ---- -**Parameters:** - -* `TOPIC` - Name of the Redpanda topic -* `SCHEMA_SUBJECT` - Schema Registry subject name (optional, defaults to TopicNameStrategy) -* `SCHEMA_LOOKUP_POLICY` - How to look up record schemas: -** `LATEST` - Use the latest schema from Schema Registry (default) -** `SCHEMA_ID` - Use the schema ID prefixed in each record -* `ERROR_HANDLING_POLICY` - How to handle deserialization failures: -** `FAIL` - Fail the query (default) -** `FILL_NULL` - Fill columns with NULL values -** `DROP_RECORD` - Skip the record -* `CONNECTION` - Connection name to use +[cols="1,3"] +|=== +| Parameter Name | Description + +| `TOPIC` +| Name of the Redpanda topic + +| `SCHEMA_SUBJECT` +| Schema Registry subject name (optional, defaults to TopicNameStrategy) + +| `SCHEMA_LOOKUP_POLICY` +a| How to look up record schemas: + +* `LATEST` - Use the latest schema from Schema Registry (default) +* `SCHEMA_ID` - Use the schema ID prefixed in each record + +| `ERROR_HANDLING_POLICY` +a| How to handle deserialization failures: + +* `FAIL` - Fail the query (default) +* `FILL_NULL` - Fill columns with NULL values +* `DROP_RECORD` - Skip the record + +| `CONNECTION` +| Connection name to use +|=== === Query the table From a1b2f3bcf2e67f8423bbab5972fc981c64cbf84c Mon Sep 17 00:00:00 2001 From: Joyce Fee Date: Wed, 4 Feb 2026 11:54:55 -0500 Subject: [PATCH 05/20] Convert Authorization privileges to table format --- modules/manage/pages/sql-engine/workshop.adoc | 28 +++++++++++++++---- 1 file changed, 22 insertions(+), 6 deletions(-) diff --git a/modules/manage/pages/sql-engine/workshop.adoc b/modules/manage/pages/sql-engine/workshop.adoc index 337580e99..5daf01e8b 100644 --- a/modules/manage/pages/sql-engine/workshop.adoc +++ b/modules/manage/pages/sql-engine/workshop.adoc @@ -164,12 +164,28 @@ Redpanda SQL Engine implements PostgreSQL-compatible role-based access control ( **Authorization:** Privileges control what users can do: -* `SELECT` - Read data from tables -* `INSERT` - Write data to tables (not supported for Redpanda-backed tables) -* `UPDATE` - Modify existing data (not supported for Redpanda-backed tables) -* `DELETE` - Remove data (not supported for Redpanda-backed tables) -* `USAGE` - Access schemas and other objects -* `CREATE` - Create new objects (tables, connections, sources) +[cols="1,3"] +|=== +| Privilege Name | Description + +| `SELECT` +| Read data from tables + +| `INSERT` +| Write data to tables (not supported for Redpanda-backed tables) + +| `UPDATE` +| Modify existing data (not supported for Redpanda-backed tables) + +| `DELETE` +| Remove data (not supported for Redpanda-backed tables) + +| `USAGE` +| Access schemas and other objects + +| `CREATE` +| Create new objects (tables, connections, sources) +|=== Use `GRANT` and `REVOKE` statements to manage access control. From 8be789b729321180e943420d057479edf35ee9c0 Mon Sep 17 00:00:00 2001 From: Joyce Fee Date: Wed, 4 Feb 2026 12:11:14 -0500 Subject: [PATCH 06/20] Convert Metadata columns to table format --- modules/manage/pages/sql-engine/workshop.adoc | 32 +++++++++++++++---- 1 file changed, 25 insertions(+), 7 deletions(-) diff --git a/modules/manage/pages/sql-engine/workshop.adoc b/modules/manage/pages/sql-engine/workshop.adoc index 5daf01e8b..a59ee8e08 100644 --- a/modules/manage/pages/sql-engine/workshop.adoc +++ b/modules/manage/pages/sql-engine/workshop.adoc @@ -304,13 +304,31 @@ WHERE c.timestamp > NOW() - INTERVAL '1 day'; All Redpanda-backed tables include metadata columns: -* `redpanda.partition` - Partition ID -* `redpanda.offset` - Record offset -* `redpanda.timestamp` - Record timestamp -* `redpanda.timestamp_source` - Timestamp source (broker or producer) -* `redpanda.headers` - Message headers -* `redpanda.key` - Raw key (populated on deserialization error with FILL_NULL policy) -* `redpanda.value` - Raw value (populated on deserialization error with FILL_NULL policy) +[cols="2,3"] +|=== +| Metadata Column Name | Description + +| `redpanda.partition` +| Partition ID + +| `redpanda.offset` +| Record offset + +| `redpanda.timestamp` +| Record timestamp + +| `redpanda.timestamp_source` +| Timestamp source (broker or producer) + +| `redpanda.headers` +| Message headers + +| `redpanda.key` +| Raw key (populated on deserialization error with FILL_NULL policy) + +| `redpanda.value` +| Raw value (populated on deserialization error with FILL_NULL policy) +|=== Query metadata columns like any other column: From b37b69a1c226f25bb13f36d118cec2e137d2ef74 Mon Sep 17 00:00:00 2001 From: Joyce Fee <102751339+Feediver1@users.noreply.github.com> Date: Wed, 4 Feb 2026 11:33:36 -0600 Subject: [PATCH 07/20] Apply suggestions from code review more wip edits --- modules/manage/pages/sql-engine/workshop.adoc | 26 +++++++++---------- 1 file changed, 13 insertions(+), 13 deletions(-) diff --git a/modules/manage/pages/sql-engine/workshop.adoc b/modules/manage/pages/sql-engine/workshop.adoc index a59ee8e08..143c9abe7 100644 --- a/modules/manage/pages/sql-engine/workshop.adoc +++ b/modules/manage/pages/sql-engine/workshop.adoc @@ -444,7 +444,7 @@ fleetmgmt operation create --type update \ === Scale down -Decrease the number of replicas to reduce resource usage: +To decrease the number of replicas to reduce resource usage: [,bash] ---- @@ -454,16 +454,16 @@ fleetmgmt operation create --type update \ --cluster-ids ---- -=== Verify scaling operation +=== Verify scaling operations -Check the operation status: +To check the operation status: [,bash] ---- fleetmgmt operation get ---- -Verify the new replica count: +To verify the new replica count: [,bash] ---- @@ -472,11 +472,11 @@ kubectl get pods -n redpanda-oxla == Delete or destroy the cluster -To remove SQL Engine from your cluster or delete the entire BYOC cluster, use Fleet Management operations. +To remove Redpanda SQL Engine from your cluster or delete the entire BYOC cluster, use Fleet Management operations. === Disable SQL Engine only -To remove SQL Engine while keeping the Redpanda cluster running: +To remove Redpanda SQL Engine while keeping the Redpanda cluster running: [,bash] ---- @@ -486,16 +486,16 @@ fleetmgmt operation create --type update \ --cluster-ids ---- -This stops all SQL Engine pods and removes the service from your data plane. +This stops all Redpanda SQL Engine pods and removes the service from your data plane. === Delete the entire BYOC cluster -To delete the BYOC cluster including SQL Engine: +To delete the BYOC cluster, including Redpanda SQL Engine: -. In the Redpanda Cloud UI, navigate to the cluster details page -. Click *Delete Cluster* -. Confirm the deletion -. Run the Terraform destroy command from your BYOC bundle directory: +. In the Redpanda Cloud Console, navigate to the cluster details page. +. Click *Delete Cluster*. +. Confirm the deletion. +. Run the Terraform **destroy** command from your BYOC bundle directory: + [,bash] ---- @@ -503,7 +503,7 @@ cd terraform destroy ---- -. Confirm the destruction when prompted +. Confirm the destruction when prompted. This removes all Redpanda and SQL Engine resources from your cloud account. From 153f027e489168242c74b6a548d388adda11755b Mon Sep 17 00:00:00 2001 From: Joyce Fee <102751339+Feediver1@users.noreply.github.com> Date: Wed, 4 Feb 2026 11:34:41 -0600 Subject: [PATCH 08/20] Update modules/manage/pages/sql-engine/workshop.adoc --- modules/manage/pages/sql-engine/workshop.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/modules/manage/pages/sql-engine/workshop.adoc b/modules/manage/pages/sql-engine/workshop.adoc index 143c9abe7..a064774ed 100644 --- a/modules/manage/pages/sql-engine/workshop.adoc +++ b/modules/manage/pages/sql-engine/workshop.adoc @@ -162,7 +162,7 @@ Redpanda SQL Engine implements PostgreSQL-compatible role-based access control ( **Authentication:** Users authenticate using username and password over PostgreSQL wire protocol. Redpanda SQL Engine supports standard PostgreSQL authentication methods including SCRAM-SHA-256. -**Authorization:** Privileges control what users can do: +For authorization, privileges control what users can do: [cols="1,3"] |=== From e0765b39409aca9ce9272aaaaa2cf78035d92b21 Mon Sep 17 00:00:00 2001 From: Joyce Fee <102751339+Feediver1@users.noreply.github.com> Date: Wed, 4 Feb 2026 11:35:00 -0600 Subject: [PATCH 09/20] Apply suggestions from code review --- modules/manage/pages/sql-engine/workshop.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/modules/manage/pages/sql-engine/workshop.adoc b/modules/manage/pages/sql-engine/workshop.adoc index a064774ed..6a531acda 100644 --- a/modules/manage/pages/sql-engine/workshop.adoc +++ b/modules/manage/pages/sql-engine/workshop.adoc @@ -432,7 +432,7 @@ You can scale SQL Engine by adjusting the number of replicas using Fleet Managem === Scale up -Increase the number of SQL Engine replicas to handle higher query loads: +To increase the number of Redpanda SQL Engine replicas to handle higher query loads: [,bash] ---- From 421db61623851134672e0df701ea4bf3e8eada8b Mon Sep 17 00:00:00 2001 From: Joyce Fee <102751339+Feediver1@users.noreply.github.com> Date: Wed, 4 Feb 2026 11:58:50 -0600 Subject: [PATCH 10/20] Update modules/manage/pages/sql-engine/workshop.adoc --- modules/manage/pages/sql-engine/workshop.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/modules/manage/pages/sql-engine/workshop.adoc b/modules/manage/pages/sql-engine/workshop.adoc index 6a531acda..f0e5d63bc 100644 --- a/modules/manage/pages/sql-engine/workshop.adoc +++ b/modules/manage/pages/sql-engine/workshop.adoc @@ -1,4 +1,4 @@ -= Redpanda SQL Engine Workshop += Redpanda SQL Engine Overview and Quickstart :description: Learn how to provision, configure, and use Redpanda SQL Engine (Oxla) with BYOC clusters to query streaming data using SQL. :page-categories: Cloud, SQL, BYOC From b91a533ede87efec52241034067ac3daa1bb9865 Mon Sep 17 00:00:00 2001 From: Joyce Fee <102751339+Feediver1@users.noreply.github.com> Date: Fri, 6 Feb 2026 14:10:36 -0600 Subject: [PATCH 11/20] Apply suggestions from code review Co-authored-by: Michele Cyran --- modules/manage/pages/sql-engine/workshop.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/modules/manage/pages/sql-engine/workshop.adoc b/modules/manage/pages/sql-engine/workshop.adoc index f0e5d63bc..695538183 100644 --- a/modules/manage/pages/sql-engine/workshop.adoc +++ b/modules/manage/pages/sql-engine/workshop.adoc @@ -1,4 +1,4 @@ -= Redpanda SQL Engine Overview and Quickstart += Redpanda SQL Engine Quickstart :description: Learn how to provision, configure, and use Redpanda SQL Engine (Oxla) with BYOC clusters to query streaming data using SQL. :page-categories: Cloud, SQL, BYOC From 04ce9c433895564db038611d8eca54edb33153d7 Mon Sep 17 00:00:00 2001 From: Joyce Fee <102751339+Feediver1@users.noreply.github.com> Date: Fri, 6 Feb 2026 14:10:55 -0600 Subject: [PATCH 12/20] Apply suggestions from code review Co-authored-by: Michele Cyran --- modules/manage/pages/sql-engine/workshop.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/modules/manage/pages/sql-engine/workshop.adoc b/modules/manage/pages/sql-engine/workshop.adoc index 695538183..173325e84 100644 --- a/modules/manage/pages/sql-engine/workshop.adoc +++ b/modules/manage/pages/sql-engine/workshop.adoc @@ -2,7 +2,7 @@ :description: Learn how to provision, configure, and use Redpanda SQL Engine (Oxla) with BYOC clusters to query streaming data using SQL. :page-categories: Cloud, SQL, BYOC -This workshop guides you through provisioning and using Redpanda SQL Engine (formerly Oxla) in a Bring Your Own Cloud (BYOC) environment. You'll learn to query Redpanda topics using standard SQL, manage users and permissions, and scale your SQL Engine deployment. +This quickstart guides you through provisioning and using Redpanda SQL Engine (formerly Oxla) in a Bring Your Own Cloud (BYOC) environment. You'll learn to query Redpanda topics using standard SQL, manage users and permissions, and scale your SQL Engine deployment. == What is Redpanda SQL Engine? From ee991f99c2439a51b79c7cfeb3d18cf427de797f Mon Sep 17 00:00:00 2001 From: Joyce Fee <102751339+Feediver1@users.noreply.github.com> Date: Fri, 6 Feb 2026 14:11:29 -0600 Subject: [PATCH 13/20] Apply suggestions from code review Co-authored-by: Michele Cyran --- modules/manage/pages/sql-engine/workshop.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/modules/manage/pages/sql-engine/workshop.adoc b/modules/manage/pages/sql-engine/workshop.adoc index 173325e84..f6ffa34b0 100644 --- a/modules/manage/pages/sql-engine/workshop.adoc +++ b/modules/manage/pages/sql-engine/workshop.adoc @@ -10,7 +10,7 @@ Redpanda SQL Engine is a SQL query engine that runs alongside your Redpanda clus From an architecture perspective, SQL Engine runs as its own cluster with a configurable number of replicas. It can be fronted by either an internal or external load balancer, allowing you to restrict access to in-cluster components (like Redpanda Connect) or expose it more broadly to applications within your VPC or to public clients. -SQL Engine integrates directly with Redpanda Schema Registry to automatically derive table schemas from your topics. This means you can immediately query topics containing Protobuf data without manually defining schemas. The engine supports standard SQL operations including JOINs, aggregations, window functions, and complex analytical queries. +SQL Engine integrates directly with Redpanda Schema Registry to automatically derive table schemas from your topics. This means you can immediately query topics containing Protobuf data without manually defining schemas. The engine supports standard SQL operations including joins, aggregations, window functions, and complex analytical queries. In Redpanda Cloud BYOC deployments, SQL Engine is deployed as an additional service inside your Redpanda data plane. It's controlled via the `redpanda_oxla` section of your cluster specification and can be enabled per cluster using Fleet Management API operations. From 14023a61a0c8d4d299b2f854c934156593e14fd5 Mon Sep 17 00:00:00 2001 From: Joyce Fee <102751339+Feediver1@users.noreply.github.com> Date: Fri, 6 Feb 2026 14:13:31 -0600 Subject: [PATCH 14/20] Apply suggestions from code review --- modules/manage/pages/sql-engine/workshop.adoc | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/modules/manage/pages/sql-engine/workshop.adoc b/modules/manage/pages/sql-engine/workshop.adoc index f6ffa34b0..2dc9db93d 100644 --- a/modules/manage/pages/sql-engine/workshop.adoc +++ b/modules/manage/pages/sql-engine/workshop.adoc @@ -23,25 +23,25 @@ SQL Engine has the following limitations in its current state: | Limitation | Description | Read-only access -| You cannot write to Redpanda-backed tables using `INSERT`, `UPDATE`, or `DELETE` statements +| You cannot write to Redpanda-backed tables using `INSERT`, `UPDATE`, or `DELETE` statements. | Protobuf only -| Tables can only be created from Redpanda topics that use Protobuf serialization with schemas stored in Schema Registry +| Tables can only be created from Redpanda topics that use Protobuf serialization with schemas stored in Schema Registry. | Schema Registry required -| Table schemas must be derived from Redpanda Schema Registry; manual schema definition is not supported +| Table schemas must be derived from Redpanda Schema Registry; manual schema definition is not supported. | Backward-compatible schemas only -| Schema evolution must be backward-compatible; breaking schema changes may cause query failures +| Schema evolution must be backward-compatible; breaking schema changes may cause query failures. | Flat structures only -| The first release supports only the `FLATTEN` struct mapping policy; compound types, variants, and JSON mapping are not yet supported +| The first release supports only the `FLATTEN` struct mapping policy; compound types, variants, and JSON mapping are not yet supported. | Single-dimensional arrays -| Arrays of arrays and nested complex types are not supported +| Arrays of arrays and nested complex types are not supported. | No streaming queries -| Queries execute in on-demand mode and return results when complete; continuous streaming queries are not supported +| Queries execute in on-demand mode and return results when complete; continuous streaming queries are not supported. | Limited type support a| Some Redpanda data types are not supported: From a065572855285c1972267f7a7870ca6d5b8aacb0 Mon Sep 17 00:00:00 2001 From: Joyce Fee <102751339+Feediver1@users.noreply.github.com> Date: Fri, 6 Feb 2026 16:34:55 -0600 Subject: [PATCH 15/20] Update modules/manage/pages/sql-engine/workshop.adoc --- modules/manage/pages/sql-engine/workshop.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/modules/manage/pages/sql-engine/workshop.adoc b/modules/manage/pages/sql-engine/workshop.adoc index 2dc9db93d..96ede76d6 100644 --- a/modules/manage/pages/sql-engine/workshop.adoc +++ b/modules/manage/pages/sql-engine/workshop.adoc @@ -12,7 +12,7 @@ From an architecture perspective, SQL Engine runs as its own cluster with a conf SQL Engine integrates directly with Redpanda Schema Registry to automatically derive table schemas from your topics. This means you can immediately query topics containing Protobuf data without manually defining schemas. The engine supports standard SQL operations including joins, aggregations, window functions, and complex analytical queries. -In Redpanda Cloud BYOC deployments, SQL Engine is deployed as an additional service inside your Redpanda data plane. It's controlled via the `redpanda_oxla` section of your cluster specification and can be enabled per cluster using Fleet Management API operations. +In Redpanda Cloud BYOC deployments, SQL Engine is deployed as an additional service inside your Redpanda data plane. It's controlled using the `redpanda_oxla` section of your cluster specification and can be enabled per cluster using Fleet Management API operations. == Limitations From 9f510375daa1fdbed0e5413a2e384fdfa2edab18 Mon Sep 17 00:00:00 2001 From: Joyce Fee <102751339+Feediver1@users.noreply.github.com> Date: Fri, 6 Feb 2026 16:35:16 -0600 Subject: [PATCH 16/20] Update modules/manage/pages/sql-engine/workshop.adoc --- modules/manage/pages/sql-engine/workshop.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/modules/manage/pages/sql-engine/workshop.adoc b/modules/manage/pages/sql-engine/workshop.adoc index 96ede76d6..d63a840b3 100644 --- a/modules/manage/pages/sql-engine/workshop.adoc +++ b/modules/manage/pages/sql-engine/workshop.adoc @@ -44,7 +44,7 @@ SQL Engine has the following limitations in its current state: | Queries execute in on-demand mode and return results when complete; continuous streaming queries are not supported. | Limited type support -a| Some Redpanda data types are not supported: +a| The following Redpanda data types are not supported: * UUID * Fixed-length binary types From 267f3dd00b5c15e85a9aa5ea23e0ef9a1d471cb1 Mon Sep 17 00:00:00 2001 From: Joyce Fee <102751339+Feediver1@users.noreply.github.com> Date: Fri, 6 Feb 2026 16:35:59 -0600 Subject: [PATCH 17/20] Update modules/manage/pages/sql-engine/workshop.adoc --- modules/manage/pages/sql-engine/workshop.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/modules/manage/pages/sql-engine/workshop.adoc b/modules/manage/pages/sql-engine/workshop.adoc index d63a840b3..03bcb20c6 100644 --- a/modules/manage/pages/sql-engine/workshop.adoc +++ b/modules/manage/pages/sql-engine/workshop.adoc @@ -53,7 +53,7 @@ a| The following Redpanda data types are not supported: * Geometry and geography types (limited support) | No consumer groups -| SQL Engine does not use Kafka consumer groups; partition assignment is handled by the query planner +| Redpanda SQL Engine does not use Kafka consumer groups; partition assignment is handled by the query planner |=== == Prerequisites From e5cf4187b4008adaa7749de6b83fb06c7a728fd8 Mon Sep 17 00:00:00 2001 From: Joyce Fee <102751339+Feediver1@users.noreply.github.com> Date: Fri, 6 Feb 2026 16:36:14 -0600 Subject: [PATCH 18/20] Update modules/manage/pages/sql-engine/workshop.adoc --- modules/manage/pages/sql-engine/workshop.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/modules/manage/pages/sql-engine/workshop.adoc b/modules/manage/pages/sql-engine/workshop.adoc index 03bcb20c6..5d9f2b6c3 100644 --- a/modules/manage/pages/sql-engine/workshop.adoc +++ b/modules/manage/pages/sql-engine/workshop.adoc @@ -58,7 +58,7 @@ a| The following Redpanda data types are not supported: == Prerequisites -Before creating a BYOC cluster with SQL Engine you must: +Before creating a BYOC cluster with Redpanda SQL Engine you must: * Have access to Redpanda Cloud and a resource group that will own the BYOC cluster * Enable (`enable-redpanda-oxla`) the feature flag for your resource group in LaunchDarkly From 5cfc2a2f41958e578c6d08bbb7c04f3e0020b614 Mon Sep 17 00:00:00 2001 From: Joyce Fee <102751339+Feediver1@users.noreply.github.com> Date: Fri, 6 Feb 2026 16:36:33 -0600 Subject: [PATCH 19/20] Update modules/manage/pages/sql-engine/workshop.adoc Co-authored-by: Michele Cyran --- modules/manage/pages/sql-engine/workshop.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/modules/manage/pages/sql-engine/workshop.adoc b/modules/manage/pages/sql-engine/workshop.adoc index 5d9f2b6c3..1aec01edc 100644 --- a/modules/manage/pages/sql-engine/workshop.adoc +++ b/modules/manage/pages/sql-engine/workshop.adoc @@ -64,7 +64,7 @@ Before creating a BYOC cluster with Redpanda SQL Engine you must: * Enable (`enable-redpanda-oxla`) the feature flag for your resource group in LaunchDarkly * Decide on the level of network exposure mode: ** Cluster-internal only (no load balancer) -** Internal load balancer (VPC/peered VPC access) +** Internal load balancer (VPC peered access) ** External load balancer (publicly accessible endpoint) == Provision Redpanda SQL Engine using BYOC From 30c2358ba139cc2421820aec4affe56b57c65935 Mon Sep 17 00:00:00 2001 From: Joyce Fee <102751339+Feediver1@users.noreply.github.com> Date: Fri, 6 Feb 2026 16:37:42 -0600 Subject: [PATCH 20/20] Update modules/manage/pages/sql-engine/workshop.adoc --- modules/manage/pages/sql-engine/workshop.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/modules/manage/pages/sql-engine/workshop.adoc b/modules/manage/pages/sql-engine/workshop.adoc index 1aec01edc..2be1b365c 100644 --- a/modules/manage/pages/sql-engine/workshop.adoc +++ b/modules/manage/pages/sql-engine/workshop.adoc @@ -88,7 +88,7 @@ cd ./bootstrap.sh ---- -. Wait for the cluster to reflect the Ready state in the Redpanda Cloud UI. +. Wait for the cluster to show the Ready state in the Redpanda Cloud UI. When the cluster provisions, Redpanda SQL Engine is automatically deployed into the same data plane because the resource group has the `enable-redpanda-oxla` feature flag enabled.