redpanda-data · JakeSCahill · May 22, 2025 · May 22, 2025 · Jun 26, 2025 · Jul 2, 2025
@@ -1,6 +1,8 @@
 name: ROOT
 title: Self-Managed
-version: 25.1
+version: 25.2
+display_version: '25.2 Beta'
+prerelease: true
 start_page: home:index.adoc
 nav:
 - modules/ROOT/nav.adoc
@@ -17,7 +19,6 @@ 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'
     latest-console-tag: 'v2.8.5'

@@ -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:
@@ -15,7 +15,7 @@ content:
   - url: .
     branches: HEAD
   - url: https://github.com/redpanda-data/docs
-    branches: [v/*, api, shared, site-search,'!v-end-of-life/*']
+    branches: [main, v/*, api, shared, site-search,'!v-end-of-life/*']
   - url: https://github.com/redpanda-data/cloud-docs
     branches: 'main'
   - url: https://github.com/redpanda-data/redpanda-labs
@@ -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:

@@ -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,7 +170,7 @@
 *** 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/query-iceberg-topics.adoc[Query Iceberg Topics]
 *** xref:manage:iceberg/iceberg-topics-databricks-unity.adoc[Query Iceberg Topics with Databricks Unity Catalog]

@@ -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:

@@ -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:
 

@@ -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.
 

@@ -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.
 

@@ -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:
 

@@ -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.

@@ -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/.

@@ -2,6 +2,9 @@
 :description: Redpanda Console supports role-based access control (RBAC) to restrict system access to authorized users. This page is intended for cluster administrators who manage Redpanda Console access and need to configure UI-based authorization.
 :page-aliases: console:single-sign-on/authorization.adoc, manage:security/console/authorization.adoc, console:features/role-bindings.adoc, console:reference/role-bindings.adoc, reference:console/role-bindings.adoc
 :page-categories: Security, Management, Redpanda Console
+:page-context-switcher: [{"name": "Redpanda Console v2.x", "to": "24.3@ROOT:console:config/security/authorization.adoc" },{"name": "Redpanda Console v3.x", "to": "current" } ]
+
+include::console:partial$operator-console-version-note.adoc[]
 
 [NOTE]
 ====
@@ -158,6 +161,8 @@ Redpanda Console provides the following predefined roles:
 | No limitations
 |===
 
+include::shared:partial$community-supported-kc.adoc[]
+
 == Grant permissions through role bindings
 
 When impersonation is disabled, Redpanda Console connects to Redpanda APIs using the service account defined in:

@@ -2,3 +2,6 @@
 :page-aliases: manage:security/console/index.adoc
 :description: Security topics for Redpanda Console.
 :page-layout: index
+:page-context-switcher: [{"name": "Redpanda Console v2.x", "to": "24.3@ROOT:console:config/security/index.adoc" },{"name": "Redpanda Console v3.x", "to": "current" } ]
+
+include::console:partial$operator-console-version-note.adoc[]
@@ -3,6 +3,9 @@
 :description: To secure Redpanda Console using TLS, you can let Redpanda Console handle TLS termination or you can offload it to an upstream component, such as a reverse proxy or a Cloud HTTPS LoadBalancer.
 :page-categories: Management, Security, Redpanda Console
 :page-exclude-related-labs: true
+:page-context-switcher: [{"name": "Redpanda Console v2.x", "to": "24.3@ROOT:console:config/security/tls-termination.adoc" },{"name": "Redpanda Console v3.x", "to": "current" } ]
+
+include::console:partial$operator-console-version-note.adoc[]
 
 To secure Redpanda Console using TLS (Transport Layer Security), you can either let Redpanda Console handle TLS termination or you can offload it to an upstream component, such as a reverse proxy or a cloud HTTPS load balancer. TLS termination refers to the process of decrypting incoming TLS-encrypted traffic. Choosing the right approach depends on various factors, such as your application's traffic load, the complexity of your infrastructure, security requirements, and resource availability:
 

@@ -1,6 +1,9 @@
 = Enable Topic Documentation in Redpanda Console
 :description: Embed your Kafka topic documentation into the Redpanda Console UI by linking a Git repository that contains the topic documentation files.
 :page-aliases: console:features/topic-documentation.adoc, manage:console/topic-documentation.adoc
+:page-context-switcher: [{"name": "Redpanda Console v2.x", "to": "24.3@ROOT:console:config/topic-documentation.adoc" },{"name": "Redpanda Console v3.x", "to": "current" } ]
+
+include::console:partial$operator-console-version-note.adoc[]
 
 You can embed your topic's documentation into the Redpanda Console user interface by providing access to a public or private Git repository that hosts your documentation files in Markdown format.
 

@@ -1,6 +1,9 @@
 = Introduction to Redpanda Console
 :description: Learn about Redpanda Console: a web interface for managing and interacting with Redpanda clusters.
 :page-aliases: console:index/index.adoc, console:features/index.adoc, reference:console/index.adoc
+:page-context-switcher: [{"name": "Redpanda Console v2.x", "to": "24.3@ROOT:console:index.adoc" },{"name": "Redpanda Console v3.x", "to": "current" } ]
+
+include::console:partial$operator-console-version-note.adoc[]
 
 Redpanda Console is a web interface for managing and interacting with Redpanda clusters. Built to provide a seamless experience for developers working with streaming data, Redpanda Console simplifies tasks associated with managing data streams, offering a UI that helps you monitor, troubleshoot, and optimize your streaming workloads.
 
@@ -45,6 +48,8 @@ image::schema-reg.png[]
 
 View and manage Kafka Connect clusters and connectors, simplifying the integration of external systems with your streaming data.
 
+include::shared:partial$community-supported-kc.adoc[]
+
 == Who should use Redpanda Console?
 
 Redpanda Console is designed for:

@@ -1,5 +1,8 @@
 = Manage Enterprise Edition Licenses through Redpanda Console
 :description: Learn how to manage Enterprise Edition licenses in Redpanda Console.
+:page-context-switcher: [{"name": "Redpanda Console v2.x", "to": "24.3@ROOT:console:ui/add-license.adoc" },{"name": "Redpanda Console v3.x", "to": "current" } ]
+
+include::console:partial$operator-console-version-note.adoc[]
 
 You can add or update an xref:get-started:licensing/overview.adoc#console[Enterprise Edition license] for both Redpanda and Redpanda Console directly through the Redpanda Console UI.
 

@@ -1,5 +1,8 @@
 = Check License Status in Redpanda Console
 :description: Learn how to check the status of your Redpanda Enterprise Edition license using the Redpanda Console. This topic includes steps to check license details and understand license warnings.
+:page-context-switcher: [{"name": "Redpanda Console v2.x", "to": "24.3@ROOT:console:ui/check-license.adoc" },{"name": "Redpanda Console v3.x", "to": "current" } ]
+
+include::console:partial$operator-console-version-note.adoc[]
 
 You can check the expiration date of a license on the **Cluster Overview** page in Redpanda Console, under the **Licensing** section.
 

@@ -1,5 +1,9 @@
 = Manage Data Transforms in {ui}
 :description: Use {ui} to monitor the status and performance metrics of your transform functions. You can also view detailed logs and delete transform functions when they are no longer needed.
+:page-context-switcher: [{"name": "Redpanda Console v2.x", "to": "24.3@ROOT:console:ui/data-transforms.adoc" },{"name": "Redpanda Console v3.x", "to": "current" } ]
+
+include::console:partial$operator-console-version-note.adoc[]
+
 // tag::single-source[]
 
 {description}

@@ -1,6 +1,10 @@
 = Edit Topic Configuration in {ui}
 :page-aliases: manage:console/edit-topic-configuration.adoc
 :description: Use {ui} to edit the configuration of existing topics in a cluster.
+:page-context-switcher: [{"name": "Redpanda Console v2.x", "to": "24.3@ROOT:console:ui/edit-topic-configuration.adoc" },{"name": "Redpanda Console v3.x", "to": "current" } ]
+
+include::console:partial$operator-console-version-note.adoc[]
+
 // tag::single-source[]
 
 {description}

@@ -1,5 +1,8 @@
 = Manage Debug Bundles in Redpanda Console
 :description: Learn how to generate, download, and delete debug bundles in Redpanda Console for comprehensive cluster diagnostics.
+:page-context-switcher: [{"name": "Redpanda Console v2.x", "to": "24.3@ROOT:console:ui/generate-bundle.adoc" },{"name": "Redpanda Console v3.x", "to": "current" } ]
+
+include::console:partial$operator-console-version-note.adoc[]
 
 [NOTE]
 ====

@@ -2,6 +2,10 @@
 :page-aliases: console:features/programmable-push-filters.adoc, reference:console/programmable-push-filters.adoc
 // Do not put page aliases in the single-sourced content
 :description: Learn how to filter Kafka records using custom JavaScript code within {ui}.
+:page-context-switcher: [{"name": "Redpanda Console v2.x", "to": "24.3@ROOT:console:ui/programmable-push-filters.adoc" },{"name": "Redpanda Console v3.x", "to": "current" } ]
+
+include::console:partial$operator-console-version-note.adoc[]
+
 // tag::single-source[]
 
 You can use push-down filters in {ui} to search through large Kafka topics that may contain millions of records. Filters are JavaScript functions executed on the backend, evaluating each record individually. Your function must return a boolean:

@@ -1,8 +1,13 @@
 = View Deserialized Messages in {ui}
 :page-aliases: console:features/record-deserialization.adoc, manage:console/protobuf.adoc, reference:console/record-deserialization.adoc
 :description: Learn how {ui} deserializes messages.
+:page-context-switcher: [{"name": "Redpanda Console v2.x", "to": "24.3@ROOT:console:ui/record-deserialization.adoc" },{"name": "Redpanda Console v3.x", "to": "current" } ]
+
+include::console:partial$operator-console-version-note.adoc[]
+
 // tag::single-source[]
 
+
 In Redpanda, the messages exchanged between producers and consumers contain raw bytes. Schemas work as an agreed-upon format, like a contract, for producers and consumers to serialize and deserialize those messages. If a producer breaks this contract, consumers can fail.
 
 {ui} automatically tries to deserialize incoming messages and displays them in human-readable format. It tests different deserialization strategies until it finds one with no errors. If no deserialization attempts are successful, {ui} renders the byte array in a hex viewer. Sometimes, the payload is displayed in hex bytes because it's encrypted or because it uses a serializer that {ui} cannot deserialize. When this happens, {ui} displays troubleshooting information. You can also download the raw bytes of the message to feed it directly to your client deserializer or share it with a support team.

@@ -2,6 +2,10 @@
 :page-aliases: manage:schema-reg/schema-reg-ui.adoc
 :page-categories: Management, Schema Registry
 :description: Perform common Schema Registry management operations in the {ui}.
+:page-context-switcher: [{"name": "Redpanda Console v2.x", "to": "24.3@ROOT:console:ui/schema-reg.adoc" },{"name": "Redpanda Console v3.x", "to": "current" } ]
+
+include::console:partial$operator-console-version-note.adoc[]
+
 // tag::single-source[]
 
 In {ui}, the *Schema Registry* menu lists registered and verified schemas, including their serialization format and versions. Select an individual schema to see which topics it applies to.

@@ -0,0 +1,21 @@
+.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.
+
+Redpanda Console configuration syntax varies by major version. Before configuring, determine which version you're using:
+
+[source,shell]
+----
+# Check console version from deployment
+kubectl get deployment -n <namespace> redpanda-console -o jsonpath='{.spec.template.spec.containers[0].image}'
+
+# Or check from running pod
+kubectl get pod -n <namespace> -l app.kubernetes.io/name=console -o jsonpath='{.items[0].spec.containers[0].image}'
+
+# Or check from console logs
+kubectl logs -n <namespace> -l app.kubernetes.io/name=console | grep "started Redpanda Console"
+----
+
+If you see output like `redpandadata/console:v2.8.0`, you're using Redpanda Console v2.x. If you see `redpandadata/console:v3.0.0`, you're using Redpanda Console v3.x.
+====