k8s: Add 25.2 beta docs for the Redpanda Operator (#1307)

Co-authored-by: Chris Seto <chriskseto@gmail.com>

Author: JakeSCahill

modules/ROOT/nav.adoc

@@ -66,6 +66,7 @@
 ** xref:deploy:redpanda/index.adoc[Redpanda]
 *** xref:deploy:redpanda/kubernetes/index.adoc[Kubernetes]
 **** xref:deploy:redpanda/kubernetes/k-deployment-overview.adoc[Overview]
+**** xref:deploy:deployment-option/self-hosted/kubernetes/k-25.2-beta.adoc[Try v25.2]
 **** xref:deploy:redpanda/kubernetes/get-started-dev.adoc[Get Started]
 ***** xref:deploy:redpanda/kubernetes/aks-guide.adoc[Azure AKS]
 ***** xref:deploy:redpanda/kubernetes/eks-guide.adoc[Amazon EKS]

modules/deploy/pages/deployment-option/self-hosted/kubernetes/k-25.2-beta.adoc

@@ -0,0 +1,121 @@
+= Try the 25.2 Beta of the Redpanda Operator
+:page-beta: true
+:description: Deploy the 25.2 beta release of the Redpanda Operator. This version of the Redpanda Operator is cluster scope so a single instance of the Operator can manage multiple Redpanda resources in different namespaces.
+
+{description}
+
+This beta version is available for testing and feedback. It is not supported by Redpanda and should not be used in production environments. To give feedback on beta releases, reach out to the Redpanda team in https://redpanda.com/slack[Redpanda Community Slack^].
+
+== Prerequisites
+
+Make sure that your Kubernetes cluster meets the xref:./k-requirements.adoc[requirements].
+
+== Install Redpanda Operator v25.2.1-beta1
+
+. Make sure that you have permission to install custom resource definitions (CRDs):
++
+```bash
+kubectl auth can-i create CustomResourceDefinition --all-namespaces
+```
++
+You should see `yes` in the output.
++
+You need these cluster-level permissions to install glossterm:cert-manager[^] and Redpanda Operator CRDs in the next steps.
+
+. Install cert-manager:
++
+```bash
+helm repo add jetstack https://charts.jetstack.io
+helm repo update
+helm install cert-manager jetstack/cert-manager \
+  --set crds.enabled=true \
+  --namespace cert-manager \
+  --create-namespace
+```
++
+TLS is enabled by default and cert-manager is used to manage TLS certificates.
+
+. Deploy the Redpanda Operator.
++
+[,bash,subs="attributes+"]
+----
+helm repo add redpanda https://charts.redpanda.com
+helm upgrade --install redpanda-controller redpanda/operator \
+  --namespace <namespace> \
+  --create-namespace \
+  --version {operator-beta-tag} \
+  --set crds.enabled=true
+----
+
+. Ensure that the Deployment is successfully rolled out:
++
+```bash
+kubectl --namespace <namespace> rollout status --watch deployment/redpanda-controller-operator
+```
++
+[.no-copy]
+----
+deployment "redpanda-controller-operator" successfully rolled out
+----
+
+. Install a xref:reference:k-crd.adoc[Redpanda custom resource] to deploy a Redpanda cluster.
++
+.`redpanda-cluster.yaml`
+[,yaml,subs="attributes+"]
+----
+apiVersion: cluster.redpanda.com/v1alpha2
+kind: Redpanda
+metadata:
+  name: redpanda
+----
+
+. If you want to use enterprise features in Redpanda, add the details of a Secret that stores your Enterprise Edition license key.
++
+.`redpanda-cluster.yaml`
+[,yaml,subs="attributes+"]
+----
+apiVersion: cluster.redpanda.com/v1alpha2
+kind: Redpanda
+metadata:
+  name: redpanda
+spec:
+  clusterSpec:
+    enterprise:
+      licenseSecretRef:
+        name: <secret-name>
+        key: <secret-key>
+----
++
+For details, see xref:get-started:licensing/add-license-redpanda/kubernetes.adoc[].
+
+. Apply the Redpanda resource:
++
+```bash
+kubectl apply -f redpanda-cluster.yaml --namespace <namespace>
+```
+
+. Wait for the Redpanda Operator to deploy the cluster:
++
+```bash
+kubectl get redpanda --namespace <namespace> --watch
+```
++
+[.no-copy]
+----
+NAME       READY   STATUS
+redpanda   True    Redpanda reconciliation succeeded
+----
++
+This step may take a few minutes. You can watch for new Pods to make sure that the deployment is progressing:
++
+```bash
+kubectl get pod --namespace <namespace>
+```
++
+If it's taking too long, see xref:manage:kubernetes/troubleshooting/k-troubleshoot.adoc[Troubleshooting].
+
+include::deploy:partial$kubernetes/guides/uninstall.adoc[leveloffset=+1]
+
+== Next steps
+
+To give feedback about this beta version, reach out to the Redpanda team in https://redpanda.com/slack[Redpanda Community Slack^].

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

@@ -9,6 +9,22 @@ See also:
 * xref:upgrade:k-compatibility.adoc[]
 * xref:upgrade:k-rolling-upgrade.adoc[]
 
+== Redpanda Operator v25.2.x (beta)
+
+link:https://github.com/redpanda-data/redpanda-operator/blob/release/v25.2.x/operator/CHANGELOG.md[Changelog^].
+
+See also: xref:deploy:deployment-option/self-hosted/kubernetes/k-25.2-beta.adoc[].
+
+=== Cluster scope by default
+
+Starting in v25.2, the Redpanda Operator defaults to cluster scope instead of namespace scope. This change provides several benefits:
+
+* **Simplified management**: A single operator instance can manage multiple Redpanda clusters across different namespaces.
+* **Reduced resource overhead**: No need to deploy separate operator instances for each namespace.
+* **Centralized upgrades**: Upgrade the operator once to benefit all managed Redpanda clusters.
+* **Cross-namespace management**: Deploy the operator in a dedicated namespace (such as `redpanda-system`) while managing clusters in application namespaces.
+* **Simplified RBAC for debug bundles**: The Redpanda Operator now provides all required permissions for `rpk` debug bundle collection by default. The `rbac.createRPKBundleCRs` flag is no longer needed.
+
 == Redpanda Operator v25.1.x (GA)
 
 link:https://github.com/redpanda-data/redpanda-operator/blob/release/v25.1.x/operator/CHANGELOG.md[Changelog^]