Cluster scope for the Redpanda Operator

antora.yml

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

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

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]

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

@@ -46,6 +46,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/kafka-connect.adoc

@@ -2,6 +2,8 @@
 :description: Connect one or more Kafka Connect clusters with Redpanda Console.
 :page-aliases: console:features/kafka-connect.adoc, manage:console/kafka-connect.adoc
 
+include::shared:partial$community-supported-kc.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.
 Redpanda Console queries all configured Kafka Connect

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

@@ -158,6 +158,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:

modules/console/pages/index.adoc

@@ -45,6 +45,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:

modules/deploy/pages/deployment-option/self-hosted/docker-image.adoc

@@ -1,6 +1,5 @@
 = Deploy Kafka Connect in Docker
 :description: Learn how to use the Docker image to configure connectors for Redpanda.
-:page-context-links: [{"name": "Docker", "to": "deploy:deployment-option/self-hosted/docker-image.adoc" },{"name": "Kubernetes", "to": "deploy:deployment-option/self-hosted/kubernetes/k-deploy-connectors.adoc" } ]
 :page-toclevels: 1
 :page-categories: Deployment, Integration
 :env-docker: true

modules/deploy/pages/deployment-option/self-hosted/kubernetes/aks-guide.adoc

@@ -126,6 +126,12 @@ To delete your Kubernetes cluster:
 az aks delete --name <cluster-name> --resource-group redpandaResourceGroup
 ----
 
+To remove the convenience alias created during the quickstart:
+
+```bash
+unalias internal-rpk
+```
+
 include::deploy:partial$kubernetes/guides/troubleshoot.adoc[leveloffset=+1]
 
 include::deploy:partial$kubernetes/guides/next-steps.adoc[leveloffset=+1]

modules/deploy/pages/deployment-option/self-hosted/kubernetes/eks-guide.adoc

@@ -373,6 +373,12 @@ To delete your Kubernetes cluster:
 eksctl delete cluster --name <cluster-name>
 ----
 
+To remove the convenience alias created during the quickstart:
+
+```bash
+unalias internal-rpk
+```
+
 include::deploy:partial$kubernetes/guides/troubleshoot.adoc[leveloffset=+1]
 
 include::deploy:partial$kubernetes/guides/next-steps.adoc[leveloffset=+1]