Prepare Kubernetes docs for 25.2 release using 25.1 helm chart/operator (#1249)

Author: JakeSCahill

modules/console/partials/operator-console-version-note.adoc

@@ -1,4 +1,4 @@
-.The Redpanda Operator deploys Redpanda Console v2.x, not v3.x
+.The Redpanda Operator deploys Redpanda Console v2.x, not v3.x.
 [%collapsible]
 ====
 Redpanda Console v3 is **not yet available when deploying with the Redpanda Operator**. The Redpanda Operator continues to deploy Redpanda Console v2. To try Redpanda Console v3 in Kubernetes, you can xref:deploy:deployment-option/self-hosted/kubernetes/k-production-deployment.adoc[deploy Redpanda using the Redpanda Helm chart] instead of the Redpanda Operator.

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

@@ -84,6 +84,8 @@ spec:
       #licenseSecretRef:
         #name: <secret-name>
         #key: <secret-key>
+    image:
+      tag: {latest-redpanda-tag}
     statefulset:
       extraVolumes: |-
         - name: redpanda-io-config
@@ -99,6 +101,7 @@ spec:
 - `metadata.name`: Name to assign the Redpanda cluster.
 - xref:reference:k-crd.adoc#k8s-api-github-com-redpanda-data-redpanda-operator-api-redpanda-v1alpha2-redpandaclusterspec[`spec.clusterSpec`]: This is where you can override default values in the Redpanda Helm chart. Here, you mount the <<prerequisites, I/O configuration file>> to the Pods that run Redpanda. For other configuration details, see <<Production considerations>>.
 - `spec.clusterSpec.enterprise`: If you want to use enterprise features in Redpanda, uncomment this section and add the details of a Secret that stores your Enterprise Edition license key. For details, see xref:get-started:licenses.adoc[].
+- `spec.clusterSpec.image.tag`: Deploys the latest version of Redpanda.
 - `spec.clusterSpec.statefulset`: Here, you mount the <<prerequisites, I/O configuration file>> to the Pods that run Redpanda. For other configuration details, see <<Production considerations>>.
 
 . Apply the Redpanda resource:
@@ -169,6 +172,8 @@ The Redpanda Helm chart enables TLS by default and uses cert-manager to manage T
 .`redpanda-values.yaml`
 [,yaml]
 ----
+image:
+  tag: {latest-redpanda-tag}
 statefulset:
   extraVolumes: |-
     - name: redpanda-io-config

modules/deploy/partials/kubernetes/guides/deploy-redpanda.adoc

@@ -57,6 +57,8 @@ metadata:
   name: redpanda
 spec:
   clusterSpec:
+    image:
+      tag: {latest-redpanda-tag}
     external:
       domain: customredpandadomain.local
     auth:
@@ -75,6 +77,7 @@ spec:
 kubectl apply -f redpanda-cluster.yaml --namespace <namespace>
 ```
 +
+- `image.tag`: Deploys the latest version of Redpanda.
 - `external.domain`: The custom domain that each broker will advertise to clients externally. This domain is added to the internal and external TLS certificates so that you can connect to the cluster using this domain.
 - `auth.sasl.name`: Creates a superuser called `superuser` that can grant permissions to new users in your cluster using access control lists (ACLs).
 - `storage.persistentVolume.storageClass`: Points each PVC associated with the Redpanda brokers to the `csi-driver-lvm-striped-xfs` StorageClass. This StorageClass allows the LVM CSI driver to provision the appropriate local PersistentVolumes backed by NVMe disks for each Redpanda broker.
@@ -127,6 +130,7 @@ helm repo update
 helm install redpanda redpanda/redpanda \
   --version {latest-redpanda-helm-chart-version} \
   --namespace <namespace> --create-namespace \
+  --set image.tag={latest-redpanda-tag} \
   --set auth.sasl.enabled=true \
   --set "auth.sasl.users[0].name=superuser" \
   --set "auth.sasl.users[0].password=secretpassword" \
@@ -136,6 +140,7 @@ helm install redpanda redpanda/redpanda \
   --timeout 1h
 ----
 +
+- `image.tag`: Deploys the latest version of Redpanda.
 - `external.domain`: The custom domain that each broker advertises to clients externally. This domain is added to the internal and external TLS certificates so that you can connect to the cluster using this domain.
 - `auth.sasl.name`: Creates a superuser called `superuser` that can grant permissions to new users in your cluster using access control lists (ACLs).
 - `storage.persistentVolume.storageClass`: Points each PVC associated with the Redpanda brokers to the `csi-driver-lvm-striped-xfs` StorageClass. This StorageClass allows the LVM CSI driver to provision the appropriate local PersistentVolumes backed by NVMe disks for each Redpanda broker.

modules/upgrade/pages/k-compatibility.adoc

@@ -11,24 +11,20 @@ include::partial$versioning.adoc[]
 
 The Redpanda Helm chart and Redpanda Operator are versioned and tested alongside specific Redpanda core releases, Kubernetes, and Helm.
 
-Starting from version v25.1.1-beta1, the Redpanda Operator and Redpanda Helm chart follow a new versioning scheme aligned with Redpanda core releases:
+Starting from version 25.1.1, the Redpanda Operator and Redpanda Helm chart follow a new versioning scheme aligned with Redpanda core releases:
 
 - `v25.1` refers to the Redpanda core feature release deployed by default.
 
 - The patch version denotes the patch version for either the operator or Helm chart. It is not the patch version of Redpanda core.
 
-- The beta version is used for pre-release versions of the Redpanda Operator and Helm chart. These versions are not intended for production use.
+NOTE: If a version includes `-beta`, it is a pre-release version of the Redpanda Operator and Helm chart. These versions are not supported and should not be used in production environments. Beta versions are available only for testing and feedback. To give feedback on beta releases, reach out to the Redpanda team in https://redpanda.com/slack[Redpanda Community Slack^].
 
 Each Redpanda Operator and Helm chart version supports the corresponding Redpanda core version plus one minor version above and one below. This approach ensures flexibility during upgrades. For example, Redpanda Operator version 25.1.1 supports Redpanda core versions 25.2.x, 25.1.x, and 24.3.x.
 
 Redpanda Operator and Helm chart versions are supported only while their associated Redpanda core version remains supported. If the core version reaches end of life (EoL), the corresponding versions of the Redpanda Operator and Helm chart also reach EoL.
 
-NOTE: Beta versions are available only for testing and feedback. They are 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^].
-
 == Kubernetes version policy
 
-The minimum supported Kubernetes version is {supported-kubernetes-version}.
-
 The Kubernetes versions listed in the compatibility matrix are suggested ranges, based on testing and reported usage. Not every patch or minor version within these ranges is explicitly tested.
 
 To request compatibility testing of a Kubernetes version outside of the given ranges, contact https://support.redpanda.com/hc/en-us/requests/new[Redpanda support^].
@@ -41,32 +37,69 @@ Redpanda Core has no direct dependency on Kubernetes. Compatibility is influence
 |===
 |Redpanda Core / `rpk` |Helm Chart |Operator Helm Chart |Operator |Helm CLI |Kubernetes
 
-// |25.2.x
-// |25.3-k8sx, 25.2-k8sx, 25.1-k8sx
-// |25.3-k8sx, 25.2-k8sx, 25.1-k8sx
-// |25.3-k8sx, 25.2-k8sx, 25.1-k8sx
-// |3.13+
-// |1.30.x - 1.33.x
+.1+|25.2.x
 
 |25.1.x
-|25.1.1-betaX, 5.10.x, 5.9.x
-|25.1.1-betaX, 2.4.x, 0.4.36
-|25.1.1-betaX, 2.4.x, 2.3.x
+|25.1.x
+|25.1.x
+|3.12+
+d|1.28.x - 1.32.x{fn-k8s-compatibility}
+
+.3+|25.1.x
+|25.1.x
+|25.1.x
+|25.1.x
 |3.12+
 // d (default) here is required to get footnotes to appear at the bottom of the page
 // instead of inside the table cell.
 // See https://github.com/asciidoctor/asciidoctor/issues/2350#issuecomment-546841684
 d|1.28.x - 1.32.x{fn-k8s-compatibility}
 
-|24.3.x
-|25.1.1-betaX, 5.9.x
-|25.1.1-betaX, 0.4.41, 0.4.36, 0.4.29
-|25.1.1-betaX, 2.4.x, 2.3.x, 2.2.x
+|5.10.x
+|2.4.x
+|2.4.x
+|3.12+
+d|1.28.x - 1.32.x{fn-k8s-compatibility}
+
+|5.9.x
+|0.4.36
+|2.3.x
+|3.12+
+d|1.28.x - 1.32.x{fn-k8s-compatibility}
+
+.4+|24.3.x
+|25.1.x
+|25.1.x
+|25.1.x
+|3.11+
+d|1.28.x - 1.32.x{fn-k8s-compatibility}
+
+|5.9.x
+|0.4.41
+|2.4.x
+|3.11+
+d|1.28.x - 1.31.x{fn-k8s-compatibility}
+
+|5.9.x
+|0.4.36
+|2.3.x
+|3.11+
+d|1.28.x - 1.31.x{fn-k8s-compatibility}
+
+|5.9.x
+|0.4.29
+|2.2.x
 |3.11+
 d|1.28.x - 1.31.x{fn-k8s-compatibility}
 
-|24.2.x
-|5.9.x, 5.8.x
+.2+|24.2.x
+|5.9.x
+|0.4.29
+|2.2.x
+|3.10+
+d|1.27.x - 1.30.x{fn-k8s-compatibility}
+
+|5.8.x
 |0.4.29
 |2.2.x
 |3.10+
@@ -90,16 +123,16 @@ Upgrading the Helm chart may also upgrade Redpanda Console. Because of this buil
 |Redpanda Console |Helm Chart |Operator
 
 |v3.x.x
-|v25.1.1-beta1
-|v25.1.1-beta1
+|25.1.x
+|Not yet supported
 
 |v2.x.x
-| 5.10.1, 5.9.x, 5.8.x
-|2.4.x, 2.3.x, 2.2.x
+|5.10.1, 5.9.x, 5.8.x
+|25.1.x, 2.4.x, 2.3.x, 2.2.x
 
 |===
 
 == Next steps
 
 - xref:deploy:deployment-option/self-hosted/kubernetes/kubernetes-deploy.adoc[Deploy Redpanda in Kubernetes]
-- xref:k-rolling-upgrade.adoc[Upgrade Redpanda in Kubernetes]
+- xref:k-rolling-upgrade.adoc[Upgrade Redpanda in Kubernetes]