Data transforms and self-service config do not work on Redpanda Cloud Serverless clusters

Before deploying a transform to Redpanda Cloud, confirm the cluster is BYOC or Dedicated on AWS or GCP and on Redpanda 24.3+; do not deploy to Serverless. Run rpk cloud login and select the cluster first, since Cloud config changes go through the control plane, not the broker Admin API. Set only properties from the Cloud 'Cluster Configuration Properties' reference; anything Redpanda manages returns REASONINVALIDINPUT. Expect restart-requiring properties to return a long-running operation ID and take several minutes.

Context: Official docs (redpanda-data/skills, rpk-transform skill): documents the Serverless-limits gotcha that trips agents deploying data transforms. Data transforms are supported on BYOC and Dedicated clusters running Redpanda 24.3+, but Serverless is not listed as supported, so transforms should not be deployed there. Self-service cluster config via rpk requires rpk 25.1.2+ and Redpanda 25.1.2+, works only on BYOC/Dedicated on AWS and GCP (not Azure, not Serverless), and only a curated subset of datatransforms* properties is settable; the rest returns REASONINVALIDINPUT.

Source: Official docs (redpanda-data/skills, rpk-transform skill): documents the Serverless-limits gotcha that trips agents deploying data transforms. Data transforms are supported on BYOC and Dedicated clusters running Redpanda 24.3+, but Serverless is not listed as supported, so transforms should not be deployed there. Self-service cluster config via rpk requires rpk 25.1.2+ and Redpanda 25.1.2+, works only on BYOC/Dedicated on AWS and GCP (not Azure, not Serverless), and only a curated subset of datatransforms* properties is settable; the rest returns REASONINVALIDINPUT.

Verified resolution: Before deploying a transform to Redpanda Cloud, confirm the cluster is BYOC or Dedicated on AWS or GCP and on Redpanda 24.3+; do not deploy to Serverless. Run rpk cloud login and select the cluster first, since Cloud config changes go through the control plane, not the broker Admin API. Set only properties from the Cloud 'Cluster Configuration Properties' reference; anything Redpanda manages returns REASONINVALIDINPUT. Expect restart-requiring properties to return a long-running operation ID and take several minutes.

Source URL: https://github.com/redpanda-data/skills/blob/HEAD/skills/rpk-transform/SKILL.md