Merge branch 'main' into DOC-1602

Author: Feediver1

antora.yml

@@ -1,13 +1,13 @@
 name: ROOT
 title: Self-Managed
-version: 25.2
+version: 25.3
 start_page: home:index.adoc
 nav:
 - modules/ROOT/nav.adoc
 asciidoc:
   attributes:
     # Date of release in the format YYYY-MM-DD
-    page-release-date: 2025-07-31
+    page-release-date: 2025-11-19
     # Only used in the main branch (latest version)
     page-header-data:
       order: 2
@@ -17,18 +17,18 @@ asciidoc:
     # Fallback versions
     # We try to fetch the latest versions from GitHub at build time
     # --
-    full-version: 25.2.1
-    latest-redpanda-tag: 'v25.2.1'
-    latest-console-tag: 'v2.8.5'
-    latest-release-commit: '68c64fd'
+    full-version: 25.3.1
+    latest-redpanda-tag: 'v25.3.1'
+    latest-console-tag: '3.30.1'
+    latest-release-commit: '6aa5af28b020b66e5caa966094882b7260497a53'
     latest-operator-version: 'v2.3.8-24.3.6'
-    operator-beta-tag: 'v25.1.1-beta1'
-    helm-beta-tag: 'v25.1.1-beta1'
-    latest-redpanda-helm-chart-version: 5.10.1
-    redpanda-beta-version: '25.1.1-rc3'
-    redpanda-beta-tag: '25.1.1-rc3'
-    console-beta-version: '3.0.0-beta.1'
-    console-beta-tag: 'v3.0.0-beta.1'
+    operator-beta-tag: ''
+    helm-beta-tag: ''
+    latest-redpanda-helm-chart-version: ''
+    redpanda-beta-version: '25.3.1-rc4'
+    redpanda-beta-tag: 'v25.3.1-rc4'
+    console-beta-version: ''
+    console-beta-tag: ''
     # --
     supported-kubernetes-version: 1.27.0-0
     supported-helm-version: 3.10.0

local-antora-playbook.yml

@@ -1,6 +1,6 @@
 site:
   title: Redpanda Docs
-  start_page: 25.2@ROOT:get-started:intro-to-events.adoc
+  start_page: ROOT:get-started:intro-to-events.adoc
   url: http://localhost:5002
   robots: disallow
   keys:

modules/ROOT/nav.adoc

@@ -86,7 +86,6 @@
 ***** xref:deploy:redpanda/manual/production/production-deployment-automation.adoc[]
 ***** xref:deploy:redpanda/manual/production/production-deployment.adoc[]
 ***** xref:deploy:redpanda/manual/production/production-readiness.adoc[]
-**** xref:deploy:redpanda/manual/high-availability.adoc[High Availability]
 **** xref:deploy:redpanda/manual/sizing-use-cases.adoc[Sizing Use Cases]
 **** xref:deploy:redpanda/manual/sizing.adoc[Sizing Guidelines]
 **** xref:deploy:redpanda/manual/linux-system-tuning.adoc[System Tuning]
@@ -163,7 +162,7 @@
 *** xref:manage:cluster-maintenance/disk-utilization.adoc[]
 *** xref:manage:cluster-maintenance/manage-throughput.adoc[Manage Throughput]
 *** xref:manage:cluster-maintenance/compaction-settings.adoc[Compaction Settings]
-*** xref:manage:cluster-maintenance/configure-availability.adoc[]
+*** xref:manage:cluster-maintenance/configure-client-connections.adoc[]
 *** xref:manage:cluster-maintenance/partition-recovery.adoc[Forced Partition Recovery]
 *** xref:manage:cluster-maintenance/nodewise-partition-recovery.adoc[Node-wise Partition Recovery]
 ** xref:manage:security/index.adoc[Security]
@@ -179,16 +178,14 @@
 *** xref:manage:tiered-storage.adoc[]
 *** xref:manage:fast-commission-decommission.adoc[]
 *** xref:manage:mountable-topics.adoc[]
-*** xref:manage:remote-read-replicas.adoc[Remote Read Replicas]
-*** xref:manage:topic-recovery.adoc[Topic Recovery]
-*** xref:manage:whole-cluster-restore.adoc[Whole Cluster Restore]
 ** xref:manage:iceberg/index.adoc[Iceberg]
 *** xref:manage:iceberg/about-iceberg-topics.adoc[About Iceberg Topics]
 *** xref:manage:iceberg/specify-iceberg-schema.adoc[Specify Iceberg Schema]
 *** xref:manage:iceberg/use-iceberg-catalogs.adoc[Use Iceberg Catalogs]
 *** xref:manage:iceberg/rest-catalog/index.adoc[Integrate with REST Catalogs]
 **** xref:manage:iceberg/iceberg-topics-aws-glue.adoc[AWS Glue]
 **** xref:manage:iceberg/iceberg-topics-databricks-unity.adoc[Databricks Unity Catalog]
+**** xref:manage:iceberg/iceberg-topics-gcp-biglake.adoc[GCP BigLake]
 **** xref:manage:iceberg/redpanda-topics-iceberg-snowflake-catalog.adoc[Snowflake and Open Catalog]
 *** xref:manage:iceberg/query-iceberg-topics.adoc[Query Iceberg Topics]
 ** xref:manage:schema-reg/index.adoc[Schema Registry]
@@ -199,6 +196,21 @@
 *** xref:manage:schema-reg/schema-reg-authorization.adoc[Schema Registry Authorization]
 *** xref:manage:schema-reg/schema-id-validation.adoc[]
 *** xref:console:ui/schema-reg.adoc[Manage in Redpanda Console]
+** xref:manage:high-availability.adoc[High Availability]
+** xref:manage:disaster-recovery/index.adoc[Disaster Recovery]
+*** xref:manage:disaster-recovery/shadowing/index.adoc[Shadowing]
+**** xref:manage:disaster-recovery/shadowing/overview.adoc[Overview]
+**** xref:manage:disaster-recovery/shadowing/setup.adoc[Configure Shadowing]
+**** xref:manage:disaster-recovery/shadowing/monitor.adoc[Monitor Shadowing]
+**** xref:manage:disaster-recovery/shadowing/failover.adoc[Configure Failover]
+**** xref:manage:disaster-recovery/shadowing/failover-runbook.adoc[Failover Runbook]
+*** xref:manage:disaster-recovery/whole-cluster-restore.adoc[Whole Cluster Restore]
+*** xref:manage:disaster-recovery/topic-recovery.adoc[Topic Recovery]
+** xref:manage:remote-read-replicas.adoc[Remote Read Replicas]
+** xref:manage:recovery-mode.adoc[Recovery Mode]
+** xref:manage:rack-awareness.adoc[Rack Awareness]
+** xref:manage:raft-group-reconfiguration.adoc[Raft Group Reconfiguration]
+** xref:manage:io-optimization.adoc[]
 ** xref:manage:console/index.adoc[Redpanda Console]
 *** xref:console:config/configure-console.adoc[Configure Redpanda Console]
 *** xref:console:config/enterprise-license.adoc[Add an Enterprise License]
@@ -212,18 +224,16 @@
 *** xref:console:config/topic-documentation.adoc[Topic Documentation]
 *** xref:console:config/analytics.adoc[Telemetry]
 *** xref:console:config/kafka-connect.adoc[Kafka Connect]
-** xref:manage:recovery-mode.adoc[Recovery Mode]
-** xref:manage:rack-awareness.adoc[Rack Awareness]
+** xref:manage:use-admin-api.adoc[Use the Admin API]
 ** xref:manage:monitoring.adoc[]
-** xref:manage:io-optimization.adoc[]
-** xref:manage:raft-group-reconfiguration.adoc[Raft Group Reconfiguration]
 * xref:upgrade:index.adoc[Upgrade]
 ** xref:upgrade:rolling-upgrade.adoc[Upgrade Redpanda in Linux]
 ** xref:upgrade:k-rolling-upgrade.adoc[Upgrade Redpanda in Kubernetes]
 ** xref:upgrade:k-upgrade-operator.adoc[Upgrade the Redpanda Operator]
 ** xref:upgrade:k-compatibility.adoc[]
 ** xref:manage:kubernetes/k-upgrade-kubernetes.adoc[Migrate Node Pools]
 ** xref:upgrade:deprecated/index.adoc[Deprecated Features]
+** xref:upgrade:iceberg-schema-changes-and-migration-guide.adoc[Iceberg Schema Changes in v25.3]
 * xref:migrate:index.adoc[Migrate]
 ** xref:migrate:console-v3.adoc[Migrate to Redpanda Console v3.0.x]
 ** xref:migrate:data-migration.adoc[]
@@ -261,6 +271,7 @@
 *** link:/api/doc/http-proxy/[HTTP Proxy API]
 *** link:/api/doc/schema-registry/[Schema Registry API]
 *** link:/api/doc/admin/[Admin API]
+*** link:/api/doc/admin/v2[Admin API (ConnectRPC)]
 ** xref:reference:data-transforms/sdks.adoc[]
 *** xref:reference:data-transforms/golang-sdk.adoc[Golang]
 *** xref:reference:data-transforms/rust-sdk.adoc[Rust]
@@ -293,6 +304,8 @@
 ***** xref:reference:rpk/rpk-cluster/rpk-cluster-config-lint.adoc[]
 ***** xref:reference:rpk/rpk-cluster/rpk-cluster-config-set.adoc[]
 ***** xref:reference:rpk/rpk-cluster/rpk-cluster-config-status.adoc[]
+**** xref:reference:rpk/rpk-cluster/rpk-cluster-connections.adoc[]
+***** xref:reference:rpk/rpk-cluster/rpk-cluster-connections-list.adoc[]
 **** xref:reference:rpk/rpk-cluster/rpk-cluster-health.adoc[]
 **** xref:reference:rpk/rpk-cluster/rpk-cluster-license.adoc[]
 ***** xref:reference:rpk/rpk-cluster/rpk-cluster-license-info.adoc[]
@@ -431,6 +444,7 @@
 ****** xref:reference:rpk/rpk-redpanda/rpk-redpanda-admin-config-log-level-set.adoc[]
 ****** xref:reference:rpk/rpk-redpanda/rpk-redpanda-admin-config-log-level.adoc[]
 ****** xref:reference:rpk/rpk-redpanda/rpk-redpanda-admin-config-print.adoc[]
+***** xref:reference:rpk/rpk-redpanda/rpk-redpanda-config-print.adoc[]
 ***** xref:reference:rpk/rpk-redpanda/rpk-redpanda-admin-partitions.adoc[]
 ****** xref:reference:rpk/rpk-redpanda/rpk-redpanda-admin-partitions.adoc[]
 ****** xref:reference:rpk/rpk-redpanda/rpk-redpanda-admin-partitions-list.adoc[]
@@ -463,6 +477,15 @@
 ***** xref:reference:rpk/rpk-security/rpk-security-user-delete.adoc[]
 ***** xref:reference:rpk/rpk-security/rpk-security-user-update.adoc[]
 ***** xref:reference:rpk/rpk-security/rpk-security-user-list.adoc[]
+*** xref:reference:rpk/rpk-shadow/rpk-shadow.adoc[]
+**** xref:reference:rpk/rpk-shadow/rpk-shadow-config-generate.adoc[]
+**** xref:reference:rpk/rpk-shadow/rpk-shadow-create.adoc[]
+**** xref:reference:rpk/rpk-shadow/rpk-shadow-delete.adoc[]
+**** xref:reference:rpk/rpk-shadow/rpk-shadow-describe.adoc[]
+**** xref:reference:rpk/rpk-shadow/rpk-shadow-failover.adoc[]
+**** xref:reference:rpk/rpk-shadow/rpk-shadow-list.adoc[]
+**** xref:reference:rpk/rpk-shadow/rpk-shadow-status.adoc[]
+**** xref:reference:rpk/rpk-shadow/rpk-shadow-update.adoc[]
 *** xref:reference:rpk/rpk-topic/rpk-topic.adoc[]
 **** xref:reference:rpk/rpk-topic/rpk-topic-add-partitions.adoc[]
 **** xref:reference:rpk/rpk-topic/rpk-topic-alter-config.adoc[]

modules/console/images/broker-overview.png

@@ -16,6 +16,8 @@ Explore a comprehensive overview of your cluster, including:
 * *Broker monitoring*: View and manage the health, status, and configurations of your brokers.
 * *Topic management*: Create, configure, and monitor topics, including detailed information on partitions, replicas, and message counts.
 * *Consumer group insights*: Track the activity and performance of your consumer groups, manage offsets, and identify potential bottlenecks.
+* xref:manage:disaster-recovery/shadowing/overview.adoc[*Shadow link management*]: Create shadow links for asynchronous, offset-preserving replication between distinct Redpanda clusters. The shadow cluster operates in read-only mode while continuously receiving updates from the source cluster. During a disaster, you can failover individual topics or an entire shadow link to make resources fully writable for production traffic.
+
 
 image::broker-overview.png[]
 

modules/console/images/overview.png

@@ -7,7 +7,7 @@ This page shows you how to deploy Redpanda Console on Linux using Docker or the
 
 == Prerequisites
 
-* You must have a running Redpanda or Kafka cluster available to connect to. Redpanda Console requires a cluster to function. For instructions on deploying a Redpanda cluster, see xref:deploy:redpanda/manual/index.adoc[].
+* You must have a running Redpanda or Kafka cluster available to connect to. Redpanda Console requires a cluster to function. For instructions on deploying a Redpanda cluster, see xref:deploy:redpanda/manual/production/index.adoc[].
 * Review the xref:deploy:console/linux/requirements.adoc[system requirements for Redpanda Console on Linux].
 
 == Deploy with Docker

modules/console/images/topic.png

@@ -318,6 +318,15 @@ In the logs, verify `enabled: 1`.
 
 See also: xref:manage:security/listener-configuration.adoc#multiple-listeners[Multiple listeners]
 
+[NOTE]
+====
+You can also use the link:api/doc/admin/operation/operation-get_security_report[`/v1/security/report`] Admin API endpoint to generate a security report for your cluster and verify TLS, authentication, and authorization settings:
+
+```bash
+curl 'http://localhost:9644/v1/security/report'
+```
+====
+
 [[redpanda-tuners]]
 === Run Redpanda tuners
 
@@ -643,6 +652,11 @@ Review your deployment automation. Specifically, if you need to reprovision a cl
 
 Check that your xref:manage:audit-logging.adoc#audit-log-flow[audit logs] are forwarded to an enterprise security information and event management (SIEM) system. 
 
+=== Monitor security settings
+
+Regularly review your cluster's security settings using the link:api/doc/admin/operation/operation-get_security_report[`/v1/security/report`] Admin API endpoint. Investigate and address any issues identified in the alerts section.
+
+include::manage:partial$security-report.adoc[]
 
 == Suggested reading
 

modules/console/pages/index.adoc

@@ -5,7 +5,7 @@ ifdef::env-kubernetes[]
 :tiered-storage: manage:kubernetes/storage/tiered-storage/k-tiered-storage.adoc
 endif::[]
 ifndef::env-kubernetes[]
-:remote-read-replicas: manage:remote-read-replicas.adoc
+:remote-read-replicas: deploy:redpanda/manual/remote-read-replicas.adoc
 :rack-awareness: manage:rack-awareness.adoc
 :tiered-storage: manage:tiered-storage.adoc
 endif::[]
@@ -48,7 +48,7 @@ Consider the following Redpanda deployment strategies for the most common types
 | Offline backups
 |===
 
-ifndef::env-kubernetes[See also: xref:./production/production-deployment.adoc[Deploy for Production]]
+ifndef::env-kubernetes[See also: xref:deploy:redpanda/manual/production/production-deployment.adoc[Deploy for Production]]
 
 == HA deployment options
 
@@ -253,7 +253,7 @@ rpk redpanda config set redpanda.rack <rackid>
 
 The modified Ansible playbooks take a per-instance rack variable from the Terraform output and use that to set the relevant cluster and broker configuration. Redpanda deployment automation can provision public cloud infrastructure with discrete failure domains (`-var=ha=true`) and use the resulting inventory to provision rack-aware clusters using Ansible.
 
-See also: xref:./production/production-deployment-automation.adoc[Automated Deployment]
+See also: xref:deploy:redpanda/manual/production/production-deployment-automation.adoc[Automated Deployment]
 
 === Single-AZ example