Release v25.2 docs (#1250)

Author: paulohtb6

antora.yml

@@ -1,6 +1,6 @@
 name: ROOT
 title: Self-Managed
-version: 25.1
+version: 25.2
 start_page: home:index.adoc
 nav:
 - modules/ROOT/nav.adoc
@@ -17,11 +17,10 @@ asciidoc:
     # Fallback versions
     # We try to fetch the latest versions from GitHub at build time
     # --
-
-    full-version: 25.1.1
-    latest-redpanda-tag: 'v25.1.1'
+    full-version: 25.2.1
+    latest-redpanda-tag: 'v25.2.1'
     latest-console-tag: 'v2.8.5'
-    latest-release-commit: 'afe1a3f'
+    latest-release-commit: '68c64fd'
     latest-operator-version: 'v2.3.8-24.3.6'
     operator-beta-tag: 'v25.1.1-beta1'
     helm-beta-tag: 'v25.1.1-beta1'

local-antora-playbook.yml

@@ -1,6 +1,6 @@
 site:
   title: Redpanda Docs
-  start_page: 25.1@ROOT:get-started:intro-to-events.adoc
+  start_page: 25.2@ROOT:get-started:intro-to-events.adoc
   url: http://localhost:5002
   robots: disallow
   keys:
@@ -43,6 +43,7 @@ antora:
   - require: '@redpanda-data/docs-extensions-and-macros/extensions/add-global-attributes'
   - require: '@redpanda-data/docs-extensions-and-macros/extensions/version-fetcher/set-latest-version'
   - require: '@redpanda-data/docs-extensions-and-macros/extensions/validate-attributes'
+  - require: '@redpanda-data/docs-extensions-and-macros/extensions/process-context-switcher'
   - require: '@redpanda-data/docs-extensions-and-macros/extensions/generate-index-data'
     data:
       sets:

modules/ROOT/nav.adoc

@@ -68,7 +68,6 @@
 *** xref:deploy:deployment-option/self-hosted/kubernetes/k-production-workflow.adoc[Deployment Workflow]
 *** xref:deploy:deployment-option/self-hosted/kubernetes/k-requirements.adoc[Requirements and Recommendations]
 *** xref:deploy:deployment-option/self-hosted/kubernetes/k-tune-workers.adoc[Tune Worker Nodes]
-*** xref:deploy:deployment-option/self-hosted/kubernetes/k-25.1-beta.adoc[Try v25.1]
 *** xref:deploy:deployment-option/self-hosted/kubernetes/kubernetes-deploy.adoc[Deploy Redpanda]
 *** xref:deploy:deployment-option/self-hosted/kubernetes/k-deploy-connectors.adoc[Deploy Connectors]
 *** xref:deploy:deployment-option/self-hosted/kubernetes/k-high-availability.adoc[High Availability]
@@ -171,17 +170,20 @@
 *** 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/choose-iceberg-mode.adoc[Choose Iceberg Mode]
+*** 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/redpanda-topics-iceberg-snowflake-catalog.adoc[Snowflake and Open Catalog]
 *** xref:manage:iceberg/query-iceberg-topics.adoc[Query Iceberg Topics]
-*** xref:manage:iceberg/iceberg-topics-databricks-unity.adoc[Query Iceberg Topics with Databricks Unity Catalog]
-*** xref:manage:iceberg/redpanda-topics-iceberg-snowflake-catalog.adoc[Query Iceberg Topics with Snowflake and Open Catalog]
 ** xref:manage:schema-reg/index.adoc[Schema Registry]
 *** xref:manage:schema-reg/schema-reg-overview.adoc[Overview]
 *** xref:manage:schema-reg/manage-schema-reg.adoc[]
 **** xref:manage:schema-reg/schema-reg-api.adoc[API]
 **** xref:console:ui/schema-reg.adoc[Redpanda Console]
 **** xref:manage:kubernetes/k-schema-controller.adoc[Kubernetes]
+*** 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:console/index.adoc[Redpanda Console]

modules/console/pages/config/configure-console.adoc

@@ -1,6 +1,9 @@
 = Configure Redpanda Console
 :description: Redpanda Console configuration file with property descriptions.
 :page-aliases: console:reference/config.adoc, reference:console/config.adoc
+:page-context-switcher: [{"name": "Redpanda Console v2.x", "to": "24.3@ROOT:console:config/configure-console.adoc" },{"name": "Redpanda Console v3.x", "to": "current" } ]
+
+include::console:partial$operator-console-version-note.adoc[]
 
 Redpanda Console loads configuration properties from three sources, in the following order of precedence:
 
@@ -46,6 +49,8 @@ KAFKA_BROKERS=redpanda-0:9092,redpanda-1:9092,redpanda-2:9092
 NOTE: You cannot use environment variables to configure object arrays, such as the configuration
 for Kafka Connect clusters. In this case, use a YAML file, and provide secrets using environment variables or command line arguments.
 
+include::shared:partial$community-supported-kc.adoc[]
+
 == Docker Compose example
 
 If you are using Docker Compose, you can mount the configuration file and set the environment variable in your `docker-compose.yml` file:

modules/console/pages/config/connect-to-redpanda.adoc

@@ -1,5 +1,8 @@
 = Configure Redpanda Console to Connect to a Redpanda Cluster
 :description: This topic provides instructions on configuring Redpanda Console to connect to a Redpanda cluster. The configuration ensures that Redpanda Console can communicate with your Redpanda brokers.
+:page-context-switcher: [{"name": "Redpanda Console v2.x", "to": "24.3@ROOT:console:config/connect-to-redpanda.adoc" },{"name": "Redpanda Console v3.x", "to": "current" } ]
+
+include::console:partial$operator-console-version-note.adoc[]
 
 Redpanda Console connects to your Redpanda cluster using dedicated configuration blocks for the Kafka API, Schema Registry API, and Admin API. Each connection serves a different purpose:
 

modules/console/pages/config/deserialization.adoc

@@ -1,5 +1,8 @@
 = Configure Message Deserialization in Redpanda Console
 :description: Configure Redpanda Console to use Schema Registry, Protobuf files, and other deserialization methods to ensure your data is correctly interpreted and displayed.
+:page-context-switcher: [{"name": "Redpanda Console v2.x", "to": "24.3@ROOT:console:config/deserialization.adoc" },{"name": "Redpanda Console v3.x", "to": "current" } ]
+
+include::console:partial$operator-console-version-note.adoc[]
 
 Redpanda Console provides tools for deserializing and inspecting messages in Kafka topics. This topic explains how to configure Redpanda Console to use Schema Registry, Protobuf files, and other deserialization methods to ensure your data is correctly interpreted and displayed.
 

modules/console/pages/config/enterprise-license.adoc

@@ -1,5 +1,8 @@
 = Add a License Key to Redpanda Console
 :description: Learn how to apply or update a license key to Redpanda Console.
+:page-context-switcher: [{"name": "Redpanda Console v2.x", "to": "24.3@ROOT:console:config/enterprise-license.adoc" },{"name": "Redpanda Console v3.x", "to": "current" } ]
+
+include::console:partial$operator-console-version-note.adoc[]
 
 To enable xref:get-started:licensing/overview.adoc#console[enterprise features for Redpanda Console], you must have an Enterprise Edition license to load at startup. This guide explains how to configure Redpanda Console to load the license key from its local configuration.
 

modules/console/pages/config/http-path-rewrites.adoc

@@ -1,6 +1,9 @@
 = HTTP Path Rewrites in Redpanda Console
 :description: Learn how to configure Redpanda Console to work seamlessly with your URL path rewrites, particularly when hosted under a subpath.
 :page-aliases: console:features/http-path-rewrites.adoc, manage:console/http-path-rewrites.adoc
+:page-context-switcher: [{"name": "Redpanda Console v2.x", "to": "24.3@ROOT:console:config/http-path-rewrites.adoc" },{"name": "Redpanda Console v3.x", "to": "current" } ]
+
+include::console:partial$operator-console-version-note.adoc[]
 
 If you want to host Redpanda Console under a subpath rather than the root path, you need to configure HTTP path rewrites. This allows you to serve Redpanda Console under a subpath of your domain, such as `+https://my-company.com/redpanda/console+`, instead of directly from `+https://my-company.com+`. This type of configuration is often necessary when:
 

modules/console/pages/config/kafka-connect.adoc

@@ -1,6 +1,11 @@
 = Connect Redpanda Console to Kafka Connect Clusters
 :description: Connect one or more Kafka Connect clusters with Redpanda Console.
 :page-aliases: console:features/kafka-connect.adoc, manage:console/kafka-connect.adoc
+:page-context-switcher: [{"name": "Redpanda Console v2.x", "to": "24.3@ROOT:console:config/kafka-connect.adoc" },{"name": "Redpanda Console v3.x", "to": "current" } ]
+
+include::shared:partial$community-supported-kc.adoc[]
+
+include::console:partial$operator-console-version-note.adoc[]
 
 Redpanda Console provides a user interface that lets you manage multiple Kafka Connect clusters.
 You can inspect or patch connectors; restart, pause, and resume connector tasks; and delete connectors.

modules/console/pages/config/security/authentication.adoc

@@ -2,6 +2,10 @@
 :description: Authentication in Redpanda Console enables users to log in and optionally forward their credentials to the connected Redpanda cluster, ensuring all API requests are executed under the user's identity.
 :page-aliases: console:single-sign-on/authentication.adoc, manage:security/console/authentication.adoc, console:config/security/plain.adoc, console:config/security/okta.adoc, console:config/security/generic-oidc.adoc, console:config/security/keycloak.adoc, console:config/security/github.adoc, console:config/security/google.adoc, console:config/security/azure-ad.adoc
 :page-categories: Security, Management, Redpanda Console
+:page-context-switcher: [{"name": "Redpanda Console v2.x", "to": "24.3@ROOT:console:config/security/authentication.adoc" },{"name": "Redpanda Console v3.x", "to": "current" } ]
+
+include::console:partial$operator-console-version-note.adoc[]
+
 
 // ========================AUTOMATED TESTS===================================
 // The comments in this file are used to run automated tests of the documented steps. Tests are run using GitHub Actions on each pull request that changes this file in the upstream repository. For more details about the testing tool we use, see https://doc-detective.com/.