docs: surface Redpanda Connect pipelines for operator users (DOC-2275)

local-antora-playbook.yml

@@ -39,6 +39,7 @@ asciidoc:
   - '@redpanda-data/docs-extensions-and-macros/macros/glossary'
   - '@redpanda-data/docs-extensions-and-macros/macros/config-ref'
   - '@redpanda-data/docs-extensions-and-macros/macros/helm-ref'
+  - '@redpanda-data/docs-extensions-and-macros/macros/badge'
   - '@redpanda-data/docs-extensions-and-macros/asciidoc-extensions/add-line-numbers-highlights'
 antora:
   extensions:

modules/ROOT/nav.adoc

@@ -110,6 +110,8 @@
 *** xref:manage:kubernetes/k-cluster-property-configuration.adoc[Cluster Properties]
 *** xref:manage:kubernetes/k-manage-topics.adoc[Manage Topics]
 *** xref:manage:kubernetes/k-manage-connectors.adoc[Manage Kafka Connect]
+*** xref:manage:kubernetes/k-connect-pipelines.adoc[Redpanda Connect Pipelines]
+**** xref:manage:kubernetes/k-autoscale-connect-pipelines.adoc[Autoscaling]
 *** xref:manage:kubernetes/storage/index.adoc[Storage]
 **** xref:manage:kubernetes/storage/k-volume-types.adoc[Volume Types]
 **** xref:manage:kubernetes/storage/k-configure-storage.adoc[Configure Storage]

modules/get-started/pages/licensing/overview.adoc

@@ -253,6 +253,26 @@ The following enterprise features are available with a valid Enterprise Edition
 
 |===
 
+[[operator]]
+=== Redpanda Operator enterprise features
+
+The Redpanda Operator gates the following Kubernetes features on a valid Enterprise Edition license. In both cases, the operator reads the license from a Secret referenced by the `enterprise.licenseSecretRef` values in the operator Helm chart.
+
+.Enterprise features in the Redpanda Operator
+[cols="1a,2a,2a"]
+|===
+| Feature | Description | Restrictions Without Valid License
+
+| xref:deploy:redpanda/kubernetes/k-stretch-clusters.adoc[Stretch Clusters] (StretchCluster resource)
+| A single logical Redpanda cluster distributed across multiple Kubernetes clusters for multi-region high availability, managed by the multicluster Redpanda Operator.
+| The multicluster operator requires a valid license to start, so stretch clusters cannot be deployed or managed without one. On a running stretch cluster, the operator continuously reports license state through the StretchCluster resource's `LicenseValid` status condition and `status.licenseStatus`, including the expiration date and any enterprise features in violation. When the license expires, the stretch cluster keeps running and its brokers' enterprise features follow the restrictions in <<redpanda-enterprise-features, table 1>>.
+
+| xref:manage:kubernetes/k-connect-pipelines.adoc[Redpanda Connect pipelines] (Pipeline resource) badge::[label=beta]
+| Run Redpanda Connect pipelines declaratively through the operator's Connect controller. Requires a license that includes the Redpanda Connect product.
+| When the license is missing, expired, invalid, or does not include the Redpanda Connect product, the operator stops creating and updating pipeline workloads: new Pipeline resources report `License: False` in their status and are never deployed, and existing pipelines keep running with their last-applied configuration but no longer receive updates. Applying a valid license resumes reconciliation automatically, without recreating any Pipeline resources.
+
+|===
+
 == Manage licenses for Redpanda
 
 Redpanda offers multiple ways to manage your license depending on your deployment method. Proper license management ensures access to advanced enterprise features and avoids restrictions when licenses are invalid or expired.
@@ -271,6 +291,24 @@ Redpanda Console offers two methods for applying or updating a license, dependin
 
 Redpanda Connect offers multiple ways to apply or update your license. See xref:connect:get-started:licensing.adoc#apply-a-license-key-to-redpanda-connect[Apply a license key to Redpanda Connect].
 
+== Manage licenses for the Redpanda Operator
+
+The Redpanda Operator reads its license from a Kubernetes Secret referenced by the `enterprise.licenseSecretRef` values in the operator Helm chart:
+
+[source,bash]
+----
+kubectl create secret generic redpanda-license \
+  --from-file=license=<path-to-license-file> \
+  --namespace <namespace>
+
+helm upgrade --install redpanda-operator redpanda/operator \
+  --namespace <namespace> \
+  --set enterprise.licenseSecretRef.name=redpanda-license \
+  --set enterprise.licenseSecretRef.key=license
+----
+
+This operator-level license gates the operator's own enterprise features, such as the <<operator, multicluster operator and the Connect controller>>. The clusters that the operator manages are licensed independently: set the `enterprise.license` or `enterprise.licenseSecretRef` field in a Redpanda or StretchCluster resource, and the operator applies that license to the cluster for you. See xref:get-started:licensing/add-license-redpanda/kubernetes.adoc[].
+
 == Next steps
 
 - xref:get-started:licensing/add-license-redpanda/index.adoc[]

modules/get-started/pages/release-notes/operator.adoc

@@ -14,6 +14,17 @@ See also:
 
 link:https://github.com/redpanda-data/redpanda-operator/blob/release/v26.2.x/operator/CHANGELOG.md[Changelog^]
 
+=== Redpanda Connect pipelines (beta)
+
+The Redpanda Operator introduces the Pipeline custom resource, which runs xref:connect:home:index.adoc[Redpanda Connect] pipelines as declaratively managed Kubernetes workloads. You define the pipeline configuration in the resource, and the operator deploys it, lints it before startup, rolls it automatically on configuration and credential changes, and reports health through status conditions. A pipeline can reference a Redpanda resource and a User resource, and the operator injects broker addresses, TLS material, and SASL credentials into the rendered configuration for you.
+
+Pipelines also implement the Kubernetes scale subresource, so you can scale them with `kubectl scale`, a HorizontalPodAutoscaler, or KEDA, including on consumer group lag and on the metrics Redpanda Connect emits.
+
+The Pipeline resource is in beta and requires an Enterprise Edition license. Enable it with the operator chart's `connectController.enabled=true` setting.
+
+* xref:manage:kubernetes/k-connect-pipelines.adoc[Run Redpanda Connect Pipelines in Kubernetes]: Deploy pipelines, connect them to clusters, and inject secrets and cloud IAM identities.
+* xref:manage:kubernetes/k-autoscale-connect-pipelines.adoc[Autoscale Redpanda Connect Pipelines]: Step-by-step HPA and KEDA autoscaling.
+
 === Stretch Clusters
 
 The Redpanda Operator introduces Stretch Clusters: a single logical Redpanda cluster distributed across multiple Kubernetes clusters for multi-region high availability. Operators in each Kubernetes cluster coordinate through Raft consensus, and the new StretchCluster and RedpandaBrokerPool custom resources define the cluster and its per-cluster broker groups.