docs (k8s): Update Kubernetes compatibility matrix for 26.1.x

modules/get-started/pages/release-notes/helm-charts.adoc

@@ -12,6 +12,18 @@ See also:
 * xref:upgrade:k-compatibility.adoc[]
 * xref:upgrade:k-rolling-upgrade.adoc[]
 
-== Redpanda chart v25.3.x
+== Console chart v26.1.x
 
-link:https://github.com/redpanda-data/redpanda-operator/blob/release/v25.3.x/charts/redpanda/CHANGELOG.md[Changelog^].
+link:https://github.com/redpanda-data/redpanda-operator/blob/release/v26.1.x/charts/console/CHANGELOG.md[Changelog^].
+
+=== Prometheus ServiceMonitor
+
+The Console Helm chart now supports deploying a Prometheus `ServiceMonitor` using `monitoring.enabled`, `monitoring.scrapeInterval`, and `monitoring.labels`. See xref:deploy:console/kubernetes/deploy.adoc#prometheus-servicemonitor[Prometheus ServiceMonitor].
+
+== Redpanda chart v26.1.x
+
+link:https://github.com/redpanda-data/redpanda-operator/blob/release/v26.1.x/charts/redpanda/CHANGELOG.md[Changelog^].
+
+=== Config-watcher sidecar resource configuration
+
+You can now configure explicit CPU and memory resource requests and limits for the config-watcher sidecar using `statefulset.sideCars.configWatcher.resources`. This is required in namespaces that enforce LimitRange or ResourceQuota policies. See xref:manage:kubernetes/k-manage-resources.adoc#config-watcher[Configure config-watcher sidecar resources].

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

@@ -10,16 +10,10 @@ See also:
 * xref:upgrade:k-rolling-upgrade.adoc[]
 
 
-== Redpanda Operator v25.3.x
+== Redpanda Operator v26.1.x
 
-link:https://github.com/redpanda-data/redpanda-operator/blob/release/v25.3.x/operator/CHANGELOG.md[Changelog^]
+link:https://github.com/redpanda-data/redpanda-operator/blob/release/v26.1.x/operator/CHANGELOG.md[Changelog^]
 
-=== ShadowLink resource for disaster recovery
+=== Prometheus ServiceMonitor for Console
 
-Redpanda Operator v25.3.x introduces the ShadowLink custom resource for managing shadow links in Kubernetes. The ShadowLink resource allows you to declaratively configure and manage disaster recovery replication between Redpanda clusters.
-
-* **Declarative configuration**: Define shadow links as Kubernetes resources with full lifecycle management.
-* **Status monitoring**: View shadow link health and replication status directly from Kubernetes.
-* **Integrated failover**: Delete the ShadowLink resource to fail over all topics.
-
-See xref:manage:kubernetes/shadowing/k-shadow-linking.adoc[Shadow Linking in Kubernetes] for setup and xref:manage:kubernetes/shadowing/k-monitor-shadowing.adoc[monitoring] documentation.
+The Console custom resource supports a `monitoring` configuration that deploys a Prometheus `ServiceMonitor` to automatically discover and scrape Console metrics. See xref:deploy:console/kubernetes/deploy.adoc#prometheus-servicemonitor[Prometheus ServiceMonitor].

modules/upgrade/pages/k-compatibility.adoc

@@ -19,7 +19,7 @@ Starting from version 25.1.1, the Redpanda Operator and Redpanda Helm chart foll
 
 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.
+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.3.1 supports Redpanda core versions 26.1.x, 25.3.x, and 25.2.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.
 
@@ -37,7 +37,30 @@ Redpanda Core has no direct dependency on Kubernetes. Compatibility is influence
 |===
 |Redpanda Core / `rpk` |Helm Chart |Operator Helm Chart |Operator |Helm CLI |Kubernetes
 
-.2+|25.3.x
+.2+|26.1.x
+
+|26.1.x
+|26.1.x
+|26.1.x
+|3.12+
+// d (default) on Kubernetes cells is required to render footnotes at the
+// bottom of the page rather than inside the table cell.
+// See https://github.com/asciidoctor/asciidoctor/issues/2350#issuecomment-546841684
+d|1.32.x - 1.35.x{fn-k8s-compatibility}
+
+|25.3.x
+|25.3.x
+|25.3.x
+|3.12+
+d|1.30.x - 1.33.x{fn-k8s-compatibility}
+
+.3+|25.3.x
+
+|26.1.x
+|26.1.x
+|26.1.x
+|3.12+
+d|1.30.x - 1.33.x{fn-k8s-compatibility}
 
 |25.3.x
 |25.3.x
@@ -70,28 +93,6 @@ d|1.30.x - 1.33.x{fn-k8s-compatibility}
 |25.1.x
 |3.12+
 d|1.28.x - 1.33.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}
-
-|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}
 |===
 
 By default, the Redpanda Helm chart depends on cert-manager for enabling TLS.
@@ -111,12 +112,8 @@ Upgrading the Helm chart may also upgrade Redpanda Console. Because of this buil
 |Redpanda Console |Helm Chart |Operator
 
 |v3.x.x
-|25.3.x, 25.2.x, 25.1.x
-|25.3.x, 25.2.x
-
-|v2.x.x
-|5.10.1, 5.9.x, 5.8.x
-|25.3.x, 25.2.x, 25.1.x, 2.4.x, 2.3.x, 2.2.x
+|26.1.x, 25.3.x, 25.2.x
+|26.1.x, 25.3.x, 25.2.x
 
 |===