From d30e92892c6889f5917a4788136ceb189c377935 Mon Sep 17 00:00:00 2001 From: JakeSCahill Date: Tue, 4 Aug 2026 14:13:36 +0100 Subject: [PATCH 1/2] fix: consolidate HA/DR nav duplication and sweep stale alias xrefs (DOC-2361) - Remove duplicate Remote Read Replicas page under tiered-storage; the kept page at manage:kubernetes/k-remote-read-replicas.adoc absorbs its aliases - Move High Availability in Kubernetes from Deploy to Manage > Kubernetes to match the Linux HA placement, with an alias for the old path - Platform-scope the two Shadowing trees: align nav labels and cross-link the disaster-recovery Shadowing index to the Kubernetes guide - Repoint all xrefs that used old deploy:deployment-option/* alias paths (and two stale manage:kubernetes/storage/* paths) at the canonical page IDs --- modules/ROOT/nav.adoc | 5 ++--- .../pages/redpanda/kubernetes/k-choose-deployment.adoc | 2 +- .../pages/redpanda/kubernetes/k-production-deployment.adoc | 6 +++--- .../pages/redpanda/kubernetes/k-production-readiness.adoc | 2 +- modules/deploy/partials/high-availability.adoc | 4 ++-- .../partials/kubernetes/guides/external-access-intro.adoc | 2 +- modules/home/pages/index.adoc | 4 ++-- .../pages/cluster-maintenance/decommission-brokers.adoc | 4 ++-- .../cluster-maintenance/node-property-configuration.adoc | 2 +- .../manage/pages/disaster-recovery/shadowing/index.adoc | 4 ++++ .../pages/kubernetes/cloud-topics/k-cloud-topics.adoc | 2 +- .../manage/pages/kubernetes/k-decommission-brokers.adoc | 6 +++--- .../pages}/kubernetes/k-high-availability.adoc | 2 +- modules/manage/pages/kubernetes/k-manage-resources.adoc | 4 ++-- modules/manage/pages/kubernetes/k-manage-topics.adoc | 2 +- .../manage/pages/kubernetes/k-remote-read-replicas.adoc | 4 ++-- modules/manage/pages/kubernetes/k-resilience-testing.adoc | 2 +- modules/manage/pages/kubernetes/k-rolling-restart.adoc | 4 ++-- modules/manage/pages/kubernetes/k-scale-redpanda.adoc | 2 +- modules/manage/pages/kubernetes/k-schema-controller.adoc | 2 +- .../pages/kubernetes/networking/external/k-nodeport.adoc | 2 +- .../pages/kubernetes/networking/k-connect-to-redpanda.adoc | 2 +- .../security/authentication/k-schema-registry-acls.adoc | 2 +- .../security/authentication/k-user-controller.adoc | 2 +- .../security/authorization/k-role-controller.adoc | 2 +- .../pages/kubernetes/shadowing/k-shadow-linking.adoc | 6 +++--- .../manage/pages/kubernetes/storage/k-volume-types.adoc | 2 +- .../kubernetes/tiered-storage/k-remote-read-replicas.adoc | 7 ------- modules/manage/partials/data-archiving.adoc | 2 +- modules/manage/partials/remote-read-replicas.adoc | 4 ++-- modules/manage/partials/whole-cluster-restore.adoc | 2 +- modules/reference/pages/k-crd.adoc | 2 +- .../pages/rpk/rpk-redpanda/rpk-redpanda-tune.adoc | 4 ++-- .../pages/rpk/rpk-transform/rpk-transform-deploy.adoc | 2 +- modules/troubleshoot/partials/errors-and-solutions.adoc | 2 +- modules/upgrade/pages/deprecated/index.adoc | 2 +- 36 files changed, 53 insertions(+), 57 deletions(-) rename modules/{deploy/pages/redpanda => manage/pages}/kubernetes/k-high-availability.adoc (79%) delete mode 100644 modules/manage/pages/kubernetes/tiered-storage/k-remote-read-replicas.adoc diff --git a/modules/ROOT/nav.adoc b/modules/ROOT/nav.adoc index 74125117fd..77c44dd25e 100644 --- a/modules/ROOT/nav.adoc +++ b/modules/ROOT/nav.adoc @@ -81,7 +81,6 @@ **** xref:deploy:redpanda/kubernetes/k-choose-deployment.adoc[Choose Your Deployment] ***** xref:deploy:redpanda/kubernetes/k-production-deployment.adoc[Deploy Redpanda] ***** xref:deploy:redpanda/kubernetes/k-stretch-clusters.adoc[Deploy a Stretch Cluster] -**** xref:deploy:redpanda/kubernetes/k-high-availability.adoc[High Availability] **** xref:deploy:redpanda/kubernetes/k-production-readiness.adoc[] *** xref:deploy:redpanda/manual/index.adoc[Linux] **** xref:deploy:redpanda/manual/production/requirements.adoc[Hardware and Software Requirements] @@ -126,7 +125,6 @@ *** xref:manage:kubernetes/tiered-storage/index.adoc[Tiered Storage] **** xref:manage:kubernetes/tiered-storage/k-tiered-storage.adoc[Use Tiered Storage] **** xref:manage:kubernetes/tiered-storage/k-fast-commission-decommission.adoc[] -**** xref:manage:kubernetes/tiered-storage/k-remote-read-replicas.adoc[Remote Read Replicas] **** xref:manage:kubernetes/tiered-storage/k-topic-recovery.adoc[Topic Recovery] **** xref:manage:kubernetes/tiered-storage/k-whole-cluster-restore.adoc[Whole Cluster Restore] *** xref:manage:kubernetes/networking/index.adoc[Networking and Connectivity] @@ -149,11 +147,12 @@ ***** xref:manage:kubernetes/security/authorization/k-group-controller.adoc[Manage Groups and ACLs (Operator)] ***** xref:manage:kubernetes/security/authentication/k-schema-registry-acls.adoc[Manage Schema Registry ACLs (Operator)] **** xref:manage:kubernetes/security/k-audit-logging.adoc[Audit Logging] +*** xref:manage:kubernetes/k-high-availability.adoc[High Availability] *** xref:manage:kubernetes/k-rack-awareness.adoc[Rack Awareness] *** xref:manage:kubernetes/k-remote-read-replicas.adoc[Remote Read Replicas] *** xref:manage:kubernetes/shadowing/index.adoc[Shadowing] **** xref:manage:kubernetes/shadowing/k-shadow-linking.adoc[Configure Shadowing] -**** xref:manage:kubernetes/shadowing/k-monitor-shadowing.adoc[Monitor] +**** xref:manage:kubernetes/shadowing/k-monitor-shadowing.adoc[Monitor Shadowing] **** xref:manage:kubernetes/shadowing/k-failover-runbook.adoc[Failover Runbook] *** xref:manage:kubernetes/k-manage-resources.adoc[Manage Pod Resources] *** xref:manage:kubernetes/k-scale-redpanda.adoc[Scale] diff --git a/modules/deploy/pages/redpanda/kubernetes/k-choose-deployment.adoc b/modules/deploy/pages/redpanda/kubernetes/k-choose-deployment.adoc index 1e29ead3d1..97435aa5fa 100644 --- a/modules/deploy/pages/redpanda/kubernetes/k-choose-deployment.adoc +++ b/modules/deploy/pages/redpanda/kubernetes/k-choose-deployment.adoc @@ -167,6 +167,6 @@ A Stretch Cluster can act as the shadow (target) cluster of a shadow link. Using == Next steps -* xref:deploy:redpanda/kubernetes/k-high-availability.adoc[High Availability in Kubernetes] for the concepts behind these topologies, including replica placement and failure modes. +* xref:manage:kubernetes/k-high-availability.adoc[High Availability in Kubernetes] for the concepts behind these topologies, including replica placement and failure modes. * xref:deploy:redpanda/kubernetes/k-production-deployment.adoc[Deploy Redpanda] or xref:deploy:redpanda/kubernetes/k-stretch-clusters.adoc[Deploy a Stretch Cluster] to get started. * xref:deploy:redpanda/kubernetes/k-production-readiness.adoc[] to validate your deployment, whichever topology you choose. diff --git a/modules/deploy/pages/redpanda/kubernetes/k-production-deployment.adoc b/modules/deploy/pages/redpanda/kubernetes/k-production-deployment.adoc index 1ff7aa931a..f3defa9c94 100644 --- a/modules/deploy/pages/redpanda/kubernetes/k-production-deployment.adoc +++ b/modules/deploy/pages/redpanda/kubernetes/k-production-deployment.adoc @@ -507,7 +507,7 @@ NOTE: You must provision one dedicated worker node for each Redpanda broker that See also: -- xref:deploy:redpanda/kubernetes/k-high-availability.adoc[] +- xref:manage:kubernetes/k-high-availability.adoc[] - xref:deploy:redpanda/kubernetes/k-requirements.adoc#number-of-worker-nodes[Kubernetes Cluster Requirements] === TLS @@ -740,7 +740,7 @@ statefulset: WARNING: Disabling `podAntiAffinity` rules is not recommended for production environments as it allows multiple brokers to be scheduled on the same node, increasing the risk of data loss if a node fails. -See also: xref:deploy:redpanda/kubernetes/k-high-availability.adoc[] +See also: xref:manage:kubernetes/k-high-availability.adoc[] === Graceful shutdown @@ -810,6 +810,6 @@ See the xref:manage:kubernetes/index.adoc[Manage Kubernetes topics] to learn how include::shared:partial$suggested-reading.adoc[] -- xref:deploy:redpanda/kubernetes/k-high-availability.adoc[] +- xref:manage:kubernetes/k-high-availability.adoc[] - xref:reference:k-redpanda-helm-spec.adoc[Redpanda Helm Specification] - xref:reference:k-crd.adoc[Redpanda CRD Reference] diff --git a/modules/deploy/pages/redpanda/kubernetes/k-production-readiness.adoc b/modules/deploy/pages/redpanda/kubernetes/k-production-readiness.adoc index ef75c37195..0354714313 100644 --- a/modules/deploy/pages/redpanda/kubernetes/k-production-readiness.adoc +++ b/modules/deploy/pages/redpanda/kubernetes/k-production-readiness.adoc @@ -911,7 +911,7 @@ See also: https://kubernetes.io/docs/tasks/run-application/configure-pdb/[Kubern === Rack awareness and topology spread -Configure topology spread constraints to distribute brokers across availability zones. For configuration instructions, see xref:deploy:redpanda/kubernetes/k-high-availability.adoc#multi-az-deployment[Multi-AZ deployment]. +Configure topology spread constraints to distribute brokers across availability zones. For configuration instructions, see xref:manage:kubernetes/k-high-availability.adoc#multi-az-deployment[Multi-AZ deployment]. Production deployments require each Redpanda broker to run in a different availability zone to ensure that a single zone failure does not cause loss of quorum. For a three-broker cluster, brokers must be distributed across three separate zones. diff --git a/modules/deploy/partials/high-availability.adoc b/modules/deploy/partials/high-availability.adoc index 12dd194ad1..699083c125 100644 --- a/modules/deploy/partials/high-availability.adoc +++ b/modules/deploy/partials/high-availability.adoc @@ -2,10 +2,10 @@ ifdef::env-kubernetes[] :remote-read-replicas: manage:kubernetes/k-remote-read-replicas.adoc :rack-awareness: manage:kubernetes/k-rack-awareness.adoc -:tiered-storage: manage:kubernetes/storage/tiered-storage/k-tiered-storage.adoc +:tiered-storage: manage:kubernetes/tiered-storage/k-tiered-storage.adoc endif::[] ifndef::env-kubernetes[] -:remote-read-replicas: deploy:redpanda/manual/remote-read-replicas.adoc +:remote-read-replicas: manage:remote-read-replicas.adoc :rack-awareness: manage:rack-awareness.adoc :tiered-storage: manage:tiered-storage.adoc endif::[] diff --git a/modules/deploy/partials/kubernetes/guides/external-access-intro.adoc b/modules/deploy/partials/kubernetes/guides/external-access-intro.adoc index d43abdb36e..f5aa1b749d 100644 --- a/modules/deploy/partials/kubernetes/guides/external-access-intro.adoc +++ b/modules/deploy/partials/kubernetes/guides/external-access-intro.adoc @@ -14,5 +14,5 @@ To access your Redpanda brokers externally, you can map your worker nodes' IP ad ==== IP addresses can change. If the IP addresses of your worker nodes change, you must update your `/etc/hosts` file with the new mappings. -In a production environment, it's a best practice to use ExternalDNS to manage DNS records for your brokers. See xref:deploy:deployment-option/self-hosted/kubernetes/k-requirements.adoc#use-externaldns-for-external-access[Use ExternalDNS for external access]. +In a production environment, it's a best practice to use ExternalDNS to manage DNS records for your brokers. See xref:deploy:redpanda/kubernetes/k-production-deployment.adoc#externaldns[Use ExternalDNS for external access]. ==== diff --git a/modules/home/pages/index.adoc b/modules/home/pages/index.adoc index 07c889e67c..b46e2af2e6 100644 --- a/modules/home/pages/index.adoc +++ b/modules/home/pages/index.adoc @@ -11,11 +11,11 @@ :page-deploy-1-icon: lightning :page-deploy-2-title: Kubernetes :page-deploy-2-desc: Deploy production-ready clusters with the Redpanda Operator. -:page-deploy-2-link: deploy:deployment-option/self-hosted/kubernetes/index.adoc +:page-deploy-2-link: deploy:redpanda/kubernetes/index.adoc :page-deploy-2-icon: kubernetes :page-deploy-3-title: Linux installation :page-deploy-3-desc: Install Redpanda on bare metal or VMs for maximum performance. -:page-deploy-3-link: deploy:deployment-option/self-hosted/manual/index.adoc +:page-deploy-3-link: deploy:redpanda/manual/index.adoc :page-deploy-3-icon: terminal // Popular topics section :page-popular-title: Popular topics diff --git a/modules/manage/pages/cluster-maintenance/decommission-brokers.adoc b/modules/manage/pages/cluster-maintenance/decommission-brokers.adoc index f8fd416f93..5deac09e19 100644 --- a/modules/manage/pages/cluster-maintenance/decommission-brokers.adoc +++ b/modules/manage/pages/cluster-maintenance/decommission-brokers.adoc @@ -85,7 +85,7 @@ ID HOST PORT RACK The output shows four racks (A/B/C/D), so you might want to have at least four brokers to make use of all racks. -Rack awareness is just one aspect of availability. Check out xref:deploy:deployment-option/self-hosted/manual/high-availability.adoc[High Availability] for details on deploying Redpanda for high availability. +Rack awareness is just one aspect of availability. Check out xref:manage:high-availability.adoc[High Availability] for details on deploying Redpanda for high availability. === Cost @@ -146,7 +146,7 @@ Cost and use case requirements dictate how much to spend on local disk capacity. ==== At this point in the example, it remains unclear whether or not it makes sense to scale down to five brokers. Current calculations are based on five brokers. You can consider other broker counts later as needed. -Additionally, assumptions have been made regarding a constant throughput and perfect data balancing. Throughput fluctuates across all partitions, which causes data imbalance. The calculations above attempt to accommodate for this by padding disk size by 1%. You can increase this buffer (for example, in the case of expected hot spot partitions). For details on sizing, see xref:deploy:deployment-option/self-hosted/manual/sizing.adoc[Sizing Guidelines]. +Additionally, assumptions have been made regarding a constant throughput and perfect data balancing. Throughput fluctuates across all partitions, which causes data imbalance. The calculations above attempt to accommodate for this by padding disk size by 1%. You can increase this buffer (for example, in the case of expected hot spot partitions). For details on sizing, see xref:deploy:redpanda/manual/sizing.adoc[Sizing Guidelines]. ==== === Durability diff --git a/modules/manage/pages/cluster-maintenance/node-property-configuration.adoc b/modules/manage/pages/cluster-maintenance/node-property-configuration.adoc index 2dbd045ac3..55436ffd12 100644 --- a/modules/manage/pages/cluster-maintenance/node-property-configuration.adoc +++ b/modules/manage/pages/cluster-maintenance/node-property-configuration.adoc @@ -16,7 +16,7 @@ The default `redpanda.yaml` file groups broker properties into categories: The `redpanda.yaml` file rarely needs to be edited after the system is installed, but you can choose to change broker configuration property values. -NOTE: The broker configuration property xref:reference:properties/broker-properties.adoc[`node_id`] is immutable. To ensure safe operations, omit the `node_id` field from `redpanda.yaml` and allow Redpanda to assign it automatically. For more information, see xref:deploy:deployment-option/self-hosted/manual/production/production-deployment.adoc#do-not-configure-broker-ids[Do not configure broker IDs]. +NOTE: The broker configuration property xref:reference:properties/broker-properties.adoc[`node_id`] is immutable. To ensure safe operations, omit the `node_id` field from `redpanda.yaml` and allow Redpanda to assign it automatically. For more information, see xref:deploy:redpanda/manual/production/production-deployment.adoc#do-not-configure-broker-ids[Do not configure broker IDs]. To change a broker property setting: diff --git a/modules/manage/pages/disaster-recovery/shadowing/index.adoc b/modules/manage/pages/disaster-recovery/shadowing/index.adoc index 8e3964085d..967507f1f5 100644 --- a/modules/manage/pages/disaster-recovery/shadowing/index.adoc +++ b/modules/manage/pages/disaster-recovery/shadowing/index.adoc @@ -5,3 +5,7 @@ :page-categories: Management, High Availability, Disaster Recovery :page-aliases: deploy:redpanda/manual/disaster-recovery/shadowing/index.adoc +ifndef::env-cloud[] +NOTE: If you deploy Redpanda in Kubernetes, see xref:manage:kubernetes/shadowing/index.adoc[Shadowing in Kubernetes] to configure shadow links with the Redpanda Operator or Helm. The topics in this section cover Shadowing concepts and the workflow for Linux deployments. +endif::[] + diff --git a/modules/manage/pages/kubernetes/cloud-topics/k-cloud-topics.adoc b/modules/manage/pages/kubernetes/cloud-topics/k-cloud-topics.adoc index faa5a3a0da..5e4ffe140d 100644 --- a/modules/manage/pages/kubernetes/cloud-topics/k-cloud-topics.adoc +++ b/modules/manage/pages/kubernetes/cloud-topics/k-cloud-topics.adoc @@ -23,7 +23,7 @@ For an overview of how Cloud Topics work, including storage modes, use cases, an You must have the following: - **kubectl**: Ensure you have the https://kubernetes.io/docs/tasks/tools/#kubectl[`kubectl`^] command-line tool installed and configured to communicate with your cluster. -- **Redpanda**: A xref:deploy:deployment-option/self-hosted/kubernetes/kubernetes-deploy.adoc[Redpanda Operator and a Redpanda resource deployed] in your Kubernetes cluster running Redpanda v26.2 or later. +- **Redpanda**: A xref:deploy:redpanda/kubernetes/k-production-deployment.adoc[Redpanda Operator and a Redpanda resource deployed] in your Kubernetes cluster running Redpanda v26.2 or later. - **Object storage**: A configured object storage backend (Amazon S3, Google Cloud Storage, Azure Blob Storage, or an S3-compatible store such as MinIO). - **Enterprise license**: A valid Redpanda Enterprise license applied to the cluster. + diff --git a/modules/manage/pages/kubernetes/k-decommission-brokers.adoc b/modules/manage/pages/kubernetes/k-decommission-brokers.adoc index 98cfc7dcb9..788090c2b1 100644 --- a/modules/manage/pages/kubernetes/k-decommission-brokers.adoc +++ b/modules/manage/pages/kubernetes/k-decommission-brokers.adoc @@ -92,7 +92,7 @@ ID HOST PORT RACK The output shows four racks (A/B/C/D), so you might want to have at least four brokers to use all racks. -Rack awareness is just one aspect of availability. Refer to xref:deploy:redpanda/kubernetes/k-high-availability.adoc[High Availability] for more details on deploying Redpanda for high availability. +Rack awareness is just one aspect of availability. Refer to xref:manage:kubernetes/k-high-availability.adoc[High Availability] for more details on deploying Redpanda for high availability. === Cost @@ -146,7 +146,7 @@ Throughput is the primary measurement required to calculate future data storage | `(200MB/sec * 3d * 1.1) = 57.024TB / 5 brokers = 11.4TB` |=== -In the example cluster, only six hours of data locally must be retained. Any older data can be moved to xref:manage:kubernetes/storage/tiered-storage/k-tiered-storage.adoc[Tiered Storage] with a retention of one year. So each broker should have 1.2TB of storage available, taking into account both throughput and current data. +In the example cluster, only six hours of data locally must be retained. Any older data can be moved to xref:manage:kubernetes/tiered-storage/k-tiered-storage.adoc[Tiered Storage] with a retention of one year. So each broker should have 1.2TB of storage available, taking into account both throughput and current data. Cost and use case requirements determine how much to spend on local disk capacity. Tiered Storage can help to both decrease costs and expand data retention capabilities. @@ -154,7 +154,7 @@ Cost and use case requirements determine how much to spend on local disk capacit ==== At this point in the example, it remains unclear whether it is safe to scale down to five brokers. Current calculations are based on five brokers. -Additionally, some assumptions have been made regarding a constant throughput and perfect data balancing. Throughput fluctuates across all partitions, which causes data imbalance. The calculations presented as examples attempt to accommodate for this by padding disk size by 1%. You can increase this buffer, for example in the case of expected hot spot partitions. For details on sizing, see xref:deploy:deployment-option/self-hosted/manual/sizing.adoc[Sizing Guidelines]. +Additionally, some assumptions have been made regarding a constant throughput and perfect data balancing. Throughput fluctuates across all partitions, which causes data imbalance. The calculations presented as examples attempt to accommodate for this by padding disk size by 1%. You can increase this buffer, for example in the case of expected hot spot partitions. For details on sizing, see xref:deploy:redpanda/manual/sizing.adoc[Sizing Guidelines]. ==== === Durability diff --git a/modules/deploy/pages/redpanda/kubernetes/k-high-availability.adoc b/modules/manage/pages/kubernetes/k-high-availability.adoc similarity index 79% rename from modules/deploy/pages/redpanda/kubernetes/k-high-availability.adoc rename to modules/manage/pages/kubernetes/k-high-availability.adoc index 928ae118f7..f651f28888 100644 --- a/modules/deploy/pages/redpanda/kubernetes/k-high-availability.adoc +++ b/modules/manage/pages/kubernetes/k-high-availability.adoc @@ -1,6 +1,6 @@ = High Availability in Kubernetes :description: Explore high availability configurations of Redpanda in Kubernetes. -:page-aliases: deploy:deployment-option/self-hosted/kubernetes/k-high-availability.adoc +:page-aliases: deploy:deployment-option/self-hosted/kubernetes/k-high-availability.adoc, deploy:redpanda/kubernetes/k-high-availability.adoc :env-kubernetes: true :page-categories: Deployment, High Availability diff --git a/modules/manage/pages/kubernetes/k-manage-resources.adoc b/modules/manage/pages/kubernetes/k-manage-resources.adoc index e74fdf909b..a4f5270ccc 100644 --- a/modules/manage/pages/kubernetes/k-manage-resources.adoc +++ b/modules/manage/pages/kubernetes/k-manage-resources.adoc @@ -9,7 +9,7 @@ Managing Pod resources, such as CPU, memory, and storage, is critical for ensuri == Prerequisites -- See xref:deploy:deployment-option/self-hosted/kubernetes/k-requirements.adoc[] for the minimum worker node, memory, CPU, and storage requirements. +- See xref:deploy:redpanda/kubernetes/k-requirements.adoc[] for the minimum worker node, memory, CPU, and storage requirements. - Make sure that your physical or virtual machines have enough resources to give to Redpanda. To see the available resources on the worker nodes that you have provisioned: + @@ -262,7 +262,7 @@ kubectl --namespace get pod -o jsonpath='{.spec.container [[qos]] == Quality of service and resource guarantees -IMPORTANT: Redpanda supports only clusters in which each broker has at least two CPU cores and the Pods that run Redpanda use the `Guaranteed` https://kubernetes.io/docs/tasks/configure-pod-container/quality-service-pod/[quality of service (QoS) class]. Clusters whose Redpanda Pods run in the `Burstable` or `BestEffort` QoS classes are not supported. For the full minimum requirements, see xref:deploy:deployment-option/self-hosted/kubernetes/k-requirements.adoc[]. +IMPORTANT: Redpanda supports only clusters in which each broker has at least two CPU cores and the Pods that run Redpanda use the `Guaranteed` https://kubernetes.io/docs/tasks/configure-pod-container/quality-service-pod/[quality of service (QoS) class]. Clusters whose Redpanda Pods run in the `Burstable` or `BestEffort` QoS classes are not supported. For the full minimum requirements, see xref:deploy:redpanda/kubernetes/k-requirements.adoc[]. To run Redpanda in the `Guaranteed` https://kubernetes.io/docs/tasks/configure-pod-container/quality-service-pod/#create-a-pod-that-gets-assigned-a-qos-class-of-guaranteed[QoS class], match resource requests and limits on all containers in the Pods that run Redpanda. diff --git a/modules/manage/pages/kubernetes/k-manage-topics.adoc b/modules/manage/pages/kubernetes/k-manage-topics.adoc index a8297e1def..d7d071e394 100644 --- a/modules/manage/pages/kubernetes/k-manage-topics.adoc +++ b/modules/manage/pages/kubernetes/k-manage-topics.adoc @@ -12,7 +12,7 @@ You must have the following: * *Kubectl*: Ensure you have the https://kubernetes.io/docs/tasks/tools/#kubectl[`kubectl`^] command-line tool installed and configured to communicate with your cluster. -* *Redpanda*: Ensure you have the xref:deploy:deployment-option/self-hosted/kubernetes/kubernetes-deploy.adoc[Redpanda Operator and a Redpanda resource deployed] in your Kubernetes cluster. +* *Redpanda*: Ensure you have the xref:deploy:redpanda/kubernetes/k-production-deployment.adoc[Redpanda Operator and a Redpanda resource deployed] in your Kubernetes cluster. == Limitations diff --git a/modules/manage/pages/kubernetes/k-remote-read-replicas.adoc b/modules/manage/pages/kubernetes/k-remote-read-replicas.adoc index d327687581..a306aa5f08 100644 --- a/modules/manage/pages/kubernetes/k-remote-read-replicas.adoc +++ b/modules/manage/pages/kubernetes/k-remote-read-replicas.adoc @@ -1,8 +1,8 @@ = Remote Read Replicas in Kubernetes :description: Create read-only topics (Remote Read Replica topics) that mirror topics on a different cluster. -:page-categories: Management, High Availability +:page-categories: Management, High Availability, Data Replication :env-kubernetes: true :tags: ["Kubernetes", "Helm configuration"] -:page-aliases: manage:kubernetes/remote-read-replicas.adoc +:page-aliases: manage:kubernetes/remote-read-replicas.adoc, manage:kubernetes/tiered-storage/k-remote-read-replicas.adoc, manage:kubernetes/storage/tiered-storage/k-remote-read-replicas.adoc include::manage:partial$remote-read-replicas.adoc[] diff --git a/modules/manage/pages/kubernetes/k-resilience-testing.adoc b/modules/manage/pages/kubernetes/k-resilience-testing.adoc index 130c32f23b..daa5e0d8ca 100644 --- a/modules/manage/pages/kubernetes/k-resilience-testing.adoc +++ b/modules/manage/pages/kubernetes/k-resilience-testing.adoc @@ -8,7 +8,7 @@ Resilience testing is an important part of ensuring that a system is reliable an == Prerequisites -* Create a test environment that mimics your production environment as closely as possible. The test environment should include a Redpanda cluster with at least three replicas, and any services that your application depends on. You can find guides for deploying Redpanda in xref:deploy:deployment-option/self-hosted/kubernetes/get-started-dev.adoc[Get Started with Redpanda in Kubernetes]. +* Create a test environment that mimics your production environment as closely as possible. The test environment should include a Redpanda cluster with at least three replicas, and any services that your application depends on. You can find guides for deploying Redpanda in xref:deploy:redpanda/kubernetes/get-started-dev.adoc[Get Started with Redpanda in Kubernetes]. * xref:./monitoring/index.adoc[Set up monitoring] so that you can observe changes in the system behavior. == Simulate failure scenarios diff --git a/modules/manage/pages/kubernetes/k-rolling-restart.adoc b/modules/manage/pages/kubernetes/k-rolling-restart.adoc index 7d7e6f47d1..c23e85b964 100644 --- a/modules/manage/pages/kubernetes/k-rolling-restart.adoc +++ b/modules/manage/pages/kubernetes/k-rolling-restart.adoc @@ -11,14 +11,14 @@ You should perform a rolling restart during operations such as configuration upd You must have the following: -* xref:deploy:deployment-option/self-hosted/kubernetes/index.adoc[A Redpanda cluster running in Kubernetes]. +* xref:deploy:redpanda/kubernetes/index.adoc[A Redpanda cluster running in Kubernetes]. * The default xref:reference:k-redpanda-helm-spec.adoc#statefulset-updatestrategy-type[RollingUpdate strategy] configured in the Helm values. == What happens during a rolling restart When you run Redpanda in Kubernetes, your Redpanda cluster is managed as a StatefulSet where each broker runs inside its own Pod. As a result, you can perform a rolling restart using the Kubernetes API to terminate one Pod at a time, starting from the one with the highest ordinal. -During a rolling restart the xref:deploy:deployment-option/self-hosted/kubernetes/k-deployment-overview.adoc[Redpanda Helm chart] automates the following procedure on each broker, using the `preStop` and `postStart` lifecycle hooks: +During a rolling restart the xref:deploy:redpanda/kubernetes/k-deployment-overview.adoc[Redpanda Helm chart] automates the following procedure on each broker, using the `preStop` and `postStart` lifecycle hooks: . The `preStop` hook is executed immediately before a container is terminated. The `preStop` hook is responsible for the following: diff --git a/modules/manage/pages/kubernetes/k-scale-redpanda.adoc b/modules/manage/pages/kubernetes/k-scale-redpanda.adoc index 1e03659dad..e7f5e6e18e 100644 --- a/modules/manage/pages/kubernetes/k-scale-redpanda.adoc +++ b/modules/manage/pages/kubernetes/k-scale-redpanda.adoc @@ -48,7 +48,7 @@ Scaling out involves adding more brokers to your Redpanda cluster. You may want To add Redpanda brokers to your cluster: -. Ensure that you have one additional worker node for each Redpanda broker that you want to add. Each Redpanda broker requires its own dedicated worker node so that it has access to all resources. For more details, see xref:deploy:deployment-option/self-hosted/kubernetes/k-requirements.adoc[]. +. Ensure that you have one additional worker node for each Redpanda broker that you want to add. Each Redpanda broker requires its own dedicated worker node so that it has access to all resources. For more details, see xref:deploy:redpanda/kubernetes/k-requirements.adoc[]. . If you use local PersistentVolumes (PV), ensure that your additional worker nodes have local disks available that meet the requirements of the configured StorageClass. See xref:manage:kubernetes/storage/k-persistent-storage.adoc[]. diff --git a/modules/manage/pages/kubernetes/k-schema-controller.adoc b/modules/manage/pages/kubernetes/k-schema-controller.adoc index 675d9c0cbc..e41000c517 100644 --- a/modules/manage/pages/kubernetes/k-schema-controller.adoc +++ b/modules/manage/pages/kubernetes/k-schema-controller.adoc @@ -10,7 +10,7 @@ Use the Schema resource to declaratively create and manage schemas as part of a Ensure you have the following: * *Kubectl*: Ensure the https://kubernetes.io/docs/tasks/tools/#kubectl[kubectl^] command-line tool is installed and configured to communicate with your cluster. -* *Redpanda cluster*: Ensure you have at least version v2.3.0-24.3.1 of the xref:deploy:deployment-option/self-hosted/kubernetes/k-production-deployment.adoc[Redpanda Operator] and a Redpanda resource deployed and accessible. +* *Redpanda cluster*: Ensure you have at least version v2.3.0-24.3.1 of the xref:deploy:redpanda/kubernetes/k-production-deployment.adoc[Redpanda Operator] and a Redpanda resource deployed and accessible. == Create a schema diff --git a/modules/manage/pages/kubernetes/networking/external/k-nodeport.adoc b/modules/manage/pages/kubernetes/networking/external/k-nodeport.adoc index 92c92d0ecf..01557c9338 100644 --- a/modules/manage/pages/kubernetes/networking/external/k-nodeport.adoc +++ b/modules/manage/pages/kubernetes/networking/external/k-nodeport.adoc @@ -13,7 +13,7 @@ image::shared:nodeport.png[A client connects to a Pod through the NodePort Servi * One worker node for each Redpanda broker that you want to deploy. * Install xref:get-started:rpk-install.adoc[rpk] on your local machine so that you can test connections to your Redpanda cluster from outside Kubernetes. -* Review xref:deploy:deployment-option/self-hosted/kubernetes/kubernetes-requirements-index.adoc[]. +* Review xref:deploy:redpanda/kubernetes/k-requirements.adoc[]. * Understand xref:manage:kubernetes/networking/k-networking-and-connectivity.adoc[Kubernetes networking for Redpanda]. * Ensure that your Kubernetes cluster is accessible through your desired node port range. For example, with AWS EKS you must edit your inbound firewall rules. And with Azure AKS, you must https://learn.microsoft.com/en-us/azure/aks/use-node-public-ips[enable public IPs] on nodes in your node pool. * If you want brokers to advertise a custom domain, you must have control over the DNS settings for that domain. diff --git a/modules/manage/pages/kubernetes/networking/k-connect-to-redpanda.adoc b/modules/manage/pages/kubernetes/networking/k-connect-to-redpanda.adoc index fef730612b..aa692fcdac 100644 --- a/modules/manage/pages/kubernetes/networking/k-connect-to-redpanda.adoc +++ b/modules/manage/pages/kubernetes/networking/k-connect-to-redpanda.adoc @@ -31,7 +31,7 @@ You must have the following: * https://kubernetes.io/docs/tasks/tools/#kubectl[Kubectl^]: Ensure you have the `kubectl` command-line tool installed and configured to communicate with your cluster. -* Redpanda cluster: xref:deploy:deployment-option/self-hosted/kubernetes/index.adoc[Deploy a Redpanda cluster]. +* Redpanda cluster: xref:deploy:redpanda/kubernetes/index.adoc[Deploy a Redpanda cluster]. == Connect to an internal cluster diff --git a/modules/manage/pages/kubernetes/security/authentication/k-schema-registry-acls.adoc b/modules/manage/pages/kubernetes/security/authentication/k-schema-registry-acls.adoc index 7f5ee61f42..ca96b8d419 100644 --- a/modules/manage/pages/kubernetes/security/authentication/k-schema-registry-acls.adoc +++ b/modules/manage/pages/kubernetes/security/authentication/k-schema-registry-acls.adoc @@ -14,7 +14,7 @@ For Schema Registry Authorization concepts and the available operations, see xre You must have the following: * *kubectl*: The https://kubernetes.io/docs/tasks/tools/#kubectl[kubectl^] command-line tool, installed and configured to communicate with your cluster. -* *Redpanda Operator v25.3 or later*: See xref:deploy:deployment-option/self-hosted/kubernetes/k-production-deployment.adoc[]. +* *Redpanda Operator v25.3 or later*: See xref:deploy:redpanda/kubernetes/k-production-deployment.adoc[]. * *Redpanda cluster with SASL enabled*: See xref:manage:kubernetes/security/authentication/k-authentication.adoc#enable[Enable SASL authentication]. * *Schema Registry Authorization enabled*: See xref:manage:schema-reg/schema-reg-authorization.adoc#enable-schema-registry-authorization[Enable Schema Registry Authorization]. diff --git a/modules/manage/pages/kubernetes/security/authentication/k-user-controller.adoc b/modules/manage/pages/kubernetes/security/authentication/k-user-controller.adoc index 5063b1420f..83083a3041 100644 --- a/modules/manage/pages/kubernetes/security/authentication/k-user-controller.adoc +++ b/modules/manage/pages/kubernetes/security/authentication/k-user-controller.adoc @@ -12,7 +12,7 @@ For role-based access control where you want to define permissions once and appl You must have the following: * *Kubectl*: Ensure you have the https://kubernetes.io/docs/tasks/tools/#kubectl[kubectl^] command-line tool installed and configured to communicate with your cluster. -* *Redpanda Operator*: Ensure you have at least version v2.2.2-24.2.4 of the xref:deploy:deployment-option/self-hosted/kubernetes/k-production-deployment.adoc[Redpanda Operator]. +* *Redpanda Operator*: Ensure you have at least version v2.2.2-24.2.4 of the xref:deploy:redpanda/kubernetes/k-production-deployment.adoc[Redpanda Operator]. * *Redpanda cluster with SASL enabled*: Ensure you have a Redpanda resource deployed with xref:manage:kubernetes/security/authentication/k-authentication.adoc#enable[SASL authentication enabled]. == Create a user diff --git a/modules/manage/pages/kubernetes/security/authorization/k-role-controller.adoc b/modules/manage/pages/kubernetes/security/authorization/k-role-controller.adoc index 89ce6e0c08..c1457915e3 100644 --- a/modules/manage/pages/kubernetes/security/authorization/k-role-controller.adoc +++ b/modules/manage/pages/kubernetes/security/authorization/k-role-controller.adoc @@ -22,7 +22,7 @@ In Redpanda, roles work the same way: You must have the following: * *Kubectl*: Ensure you have the https://kubernetes.io/docs/tasks/tools/#kubectl[kubectl^] command-line tool installed and configured to communicate with your cluster. -* *Redpanda Operator*: Ensure you have at least version 25.2 of the xref:deploy:deployment-option/self-hosted/kubernetes/k-production-deployment.adoc[Redpanda Operator]. +* *Redpanda Operator*: Ensure you have at least version 25.2 of the xref:deploy:redpanda/kubernetes/k-production-deployment.adoc[Redpanda Operator]. * *Redpanda cluster with SASL enabled*: Ensure you have a Redpanda resource deployed with xref:manage:kubernetes/security/authentication/k-authentication.adoc#enable[SASL authentication enabled]. * *Existing users*: If you plan to assign users to roles, ensure the users already exist in your Redpanda cluster. You can create users using xref:manage:kubernetes/security/authentication/k-user-controller.adoc[User resources]. diff --git a/modules/manage/pages/kubernetes/shadowing/k-shadow-linking.adoc b/modules/manage/pages/kubernetes/shadowing/k-shadow-linking.adoc index a355709523..95a1b3723d 100644 --- a/modules/manage/pages/kubernetes/shadowing/k-shadow-linking.adoc +++ b/modules/manage/pages/kubernetes/shadowing/k-shadow-linking.adoc @@ -19,8 +19,8 @@ For conceptual information about Shadowing, see xref:manage:disaster-recovery/sh === License and version requirements * Both clusters must be running Redpanda v25.3 or later. -* xref:deploy:deployment-option/self-hosted/kubernetes/k-deployment-overview.adoc[Redpanda Operator version 25.3.1 or later] (for Operator deployments). -* xref:deploy:deployment-option/self-hosted/kubernetes/k-deployment-overview.adoc[Redpanda Helm chart version 25.3.1 or later] (for Helm deployments). +* xref:deploy:redpanda/kubernetes/k-deployment-overview.adoc[Redpanda Operator version 25.3.1 or later] (for Operator deployments). +* xref:deploy:redpanda/kubernetes/k-deployment-overview.adoc[Redpanda Helm chart version 25.3.1 or later] (for Helm deployments). * You must have xref:get-started:licensing/overview.adoc[Enterprise Edition] licenses on both clusters. * If using Redpanda Console, ensure it is running v3.30 or later for managing Shadowing. @@ -40,7 +40,7 @@ For Kubernetes-specific networking configuration, see xref:manage:kubernetes/net == Deploy Redpanda clusters -Deploy both your source and shadow Redpanda clusters with Shadowing enabled. See xref:deploy:deployment-option/self-hosted/kubernetes/k-deployment-overview.adoc[Deploy Redpanda in Kubernetes] for full deployment instructions. +Deploy both your source and shadow Redpanda clusters with Shadowing enabled. See xref:deploy:redpanda/kubernetes/k-deployment-overview.adoc[Deploy Redpanda in Kubernetes] for full deployment instructions. == Create a shadow link diff --git a/modules/manage/pages/kubernetes/storage/k-volume-types.adoc b/modules/manage/pages/kubernetes/storage/k-volume-types.adoc index 1979bb8c77..586df0f239 100644 --- a/modules/manage/pages/kubernetes/storage/k-volume-types.adoc +++ b/modules/manage/pages/kubernetes/storage/k-volume-types.adoc @@ -174,7 +174,7 @@ include::shared:partial$suggested-reading.adoc[] ** link:https://kubernetes.io/docs/concepts/storage/volumes/#hostpath[hostPath volumes^] ** link:https://kubernetes.io/docs/concepts/storage/volumes/#emptydir[emptyDir volumes^] -- xref:deploy:deployment-option/self-hosted/kubernetes/k-requirements.adoc[] +- xref:deploy:redpanda/kubernetes/k-requirements.adoc[] == Next steps diff --git a/modules/manage/pages/kubernetes/tiered-storage/k-remote-read-replicas.adoc b/modules/manage/pages/kubernetes/tiered-storage/k-remote-read-replicas.adoc deleted file mode 100644 index d4624de4ca..0000000000 --- a/modules/manage/pages/kubernetes/tiered-storage/k-remote-read-replicas.adoc +++ /dev/null @@ -1,7 +0,0 @@ -= Remote Read Replicas in Kubernetes -:description: Learn how to create a Remote Read Replica topic, which is a read-only topic that mirrors a topic on a different cluster. -:page-categories: Management, High Availability, Data Replication -:env-kubernetes: true -:page-aliases: manage:kubernetes/storage/tiered-storage/k-remote-read-replicas.adoc - -include::manage:partial$remote-read-replicas.adoc[] diff --git a/modules/manage/partials/data-archiving.adoc b/modules/manage/partials/data-archiving.adoc index 93f824b0ca..289d103317 100644 --- a/modules/manage/partials/data-archiving.adoc +++ b/modules/manage/partials/data-archiving.adoc @@ -4,7 +4,7 @@ include::shared:partial$enterprise-license.adoc[] ==== ifdef::env-kubernetes[] -:tiered-storage-link: manage:kubernetes/storage/tiered-storage/k-tiered-storage.adoc +:tiered-storage-link: manage:kubernetes/tiered-storage/k-tiered-storage.adoc endif::[] ifndef::env-kubernetes[] :tiered-storage-link: manage:tiered-storage.adoc diff --git a/modules/manage/partials/remote-read-replicas.adoc b/modules/manage/partials/remote-read-replicas.adoc index bdf9de647f..6af55ef937 100644 --- a/modules/manage/partials/remote-read-replicas.adoc +++ b/modules/manage/partials/remote-read-replicas.adoc @@ -5,8 +5,8 @@ include::shared:partial$enterprise-license.adoc[] ifdef::env-kubernetes[] -:tiered-storage-link: manage:kubernetes/storage/tiered-storage/k-tiered-storage.adoc -:data-archiving-link: manage:kubernetes/storage/tiered-storage/k-tiered-storage.adoc#data-archiving +:tiered-storage-link: manage:kubernetes/tiered-storage/k-tiered-storage.adoc +:data-archiving-link: manage:kubernetes/tiered-storage/k-tiered-storage.adoc#data-archiving endif::[] ifndef::env-kubernetes[] :tiered-storage-link: manage:tiered-storage.adoc diff --git a/modules/manage/partials/whole-cluster-restore.adoc b/modules/manage/partials/whole-cluster-restore.adoc index 62bcca0fa5..bc215754dc 100644 --- a/modules/manage/partials/whole-cluster-restore.adoc +++ b/modules/manage/partials/whole-cluster-restore.adoc @@ -1,5 +1,5 @@ ifdef::env-kubernetes[] -:link-tiered-storage: manage:kubernetes/storage/tiered-storage/k-tiered-storage.adoc +:link-tiered-storage: manage:kubernetes/tiered-storage/k-tiered-storage.adoc :link-recovery-mode: manage:kubernetes/k-recovery-mode.adoc endif::[] ifndef::env-kubernetes[] diff --git a/modules/reference/pages/k-crd.adoc b/modules/reference/pages/k-crd.adoc index 6a4849a8ce..a119182778 100644 --- a/modules/reference/pages/k-crd.adoc +++ b/modules/reference/pages/k-crd.adoc @@ -2922,7 +2922,7 @@ documentation](https://kubernetes.io/docs/concepts/scheduling-eviction/assign-po [id="{anchor_prefix}-github-com-redpanda-data-redpanda-operator-operator-api-redpanda-v1alpha2-redpandaconnectors"] == RedpandaConnectors -RedpandaConnectors configures Redpanda Connectors. Redpanda Connectors is a package that includes Kafka Connect and built-in connectors, sometimes known as plugins. See xref:deploy:deployment-option/self-hosted/kubernetes/k-deploy-connectors.adoc[]. +RedpandaConnectors configures Redpanda Connectors. Redpanda Connectors is a package that includes Kafka Connect and built-in connectors, sometimes known as plugins. See xref:deploy:kafka-connect/k-deploy-kafka-connect.adoc[]. diff --git a/modules/reference/pages/rpk/rpk-redpanda/rpk-redpanda-tune.adoc b/modules/reference/pages/rpk/rpk-redpanda/rpk-redpanda-tune.adoc index 3e52e4544d..6e68b004ca 100644 --- a/modules/reference/pages/rpk/rpk-redpanda/rpk-redpanda-tune.adoc +++ b/modules/reference/pages/rpk/rpk-redpanda/rpk-redpanda-tune.adoc @@ -142,8 +142,8 @@ See also the xref:./rpk-redpanda-tune-list.adoc#tuners[Tuners reference] for des === Related topics -* xref:deploy:deployment-option/self-hosted/manual/production/production-deployment.adoc[Deploy for Production] -* xref:deploy:deployment-option/self-hosted/kubernetes/k-tune-workers.adoc[Tune Kubernetes Worker Nodes for Production] +* xref:deploy:redpanda/manual/production/production-deployment.adoc[Deploy for Production] +* xref:deploy:redpanda/kubernetes/k-tune-workers.adoc[Tune Kubernetes Worker Nodes for Production] * xref:./rpk-redpanda-mode.adoc[`rpk redpanda mode production`] * xref:./rpk-redpanda-tune-list.adoc[`rpk redpanda tune list`] diff --git a/modules/reference/pages/rpk/rpk-transform/rpk-transform-deploy.adoc b/modules/reference/pages/rpk/rpk-transform/rpk-transform-deploy.adoc index 200d510118..e79f4ed668 100644 --- a/modules/reference/pages/rpk/rpk-transform/rpk-transform-deploy.adoc +++ b/modules/reference/pages/rpk/rpk-transform/rpk-transform-deploy.adoc @@ -112,7 +112,7 @@ rpk transform deploy --compression ifndef::env-cloud[] Enabling compression may increase computation costs and could impact latency at the output topic. -For more details, see xref:deploy:deployment-option/self-hosted/manual/sizing.adoc[Sizing for Production]. +For more details, see xref:deploy:redpanda/manual/sizing.adoc[Sizing for Production]. endif::[] // end::single-source[] diff --git a/modules/troubleshoot/partials/errors-and-solutions.adoc b/modules/troubleshoot/partials/errors-and-solutions.adoc index dc9b613f51..db1a36f7e5 100644 --- a/modules/troubleshoot/partials/errors-and-solutions.adoc +++ b/modules/troubleshoot/partials/errors-and-solutions.adoc @@ -399,7 +399,7 @@ To avoid future crash loop backoffs and manage the accumulation of small segment * xref:manage:kubernetes/monitoring/k-monitor-redpanda.adoc[Monitor] the size and number of segments regularly. * Optimize your Redpanda configuration for segment management. -* Consider implementing xref:manage:kubernetes/storage/tiered-storage/k-tiered-storage.adoc[Tiered Storage] to manage data more efficiently. +* Consider implementing xref:manage:kubernetes/tiered-storage/k-tiered-storage.adoc[Tiered Storage] to manage data more efficiently. endif::[] //end::crashloopbackoff[] diff --git a/modules/upgrade/pages/deprecated/index.adoc b/modules/upgrade/pages/deprecated/index.adoc index 0cb44b83ce..d415b52c69 100644 --- a/modules/upgrade/pages/deprecated/index.adoc +++ b/modules/upgrade/pages/deprecated/index.adoc @@ -394,7 +394,7 @@ ifndef::env-cloud[] | Support for multiple Redpanda Operator instances | Operator v25.1.x -| Deploying multiple instances of the Redpanda Operator in a single Kubernetes cluster is deprecated as of v25.1.x. Only one Operator instance per cluster is supported. See xref:deploy:deployment-option/self-hosted/kubernetes/k-production-deployment.adoc[]. +| Deploying multiple instances of the Redpanda Operator in a single Kubernetes cluster is deprecated as of v25.1.x. Only one Operator instance per cluster is supported. See xref:deploy:redpanda/kubernetes/k-production-deployment.adoc[]. | The NodeWatcher and Decommission controllers. | Helm chart v5.9.21 From c77473da29d9ce543aa9cf6740956906267d813b Mon Sep 17 00:00:00 2001 From: JakeSCahill Date: Tue, 4 Aug 2026 15:58:24 +0100 Subject: [PATCH 2/2] style: lead the Shadowing index with intro prose instead of an admonition Review against docs team standards: index pages open with an intro paragraph, not a NOTE, and the Kubernetes deployment method is the Redpanda Operator or Helm chart, matching k-shadow-linking's wording. --- modules/manage/pages/disaster-recovery/shadowing/index.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/modules/manage/pages/disaster-recovery/shadowing/index.adoc b/modules/manage/pages/disaster-recovery/shadowing/index.adoc index 967507f1f5..2144332da9 100644 --- a/modules/manage/pages/disaster-recovery/shadowing/index.adoc +++ b/modules/manage/pages/disaster-recovery/shadowing/index.adoc @@ -6,6 +6,6 @@ :page-aliases: deploy:redpanda/manual/disaster-recovery/shadowing/index.adoc ifndef::env-cloud[] -NOTE: If you deploy Redpanda in Kubernetes, see xref:manage:kubernetes/shadowing/index.adoc[Shadowing in Kubernetes] to configure shadow links with the Redpanda Operator or Helm. The topics in this section cover Shadowing concepts and the workflow for Linux deployments. +These topics cover Shadowing concepts and the configuration workflow for Linux deployments. If you deploy Redpanda in Kubernetes, see xref:manage:kubernetes/shadowing/index.adoc[Shadowing in Kubernetes] to configure shadow links with the Redpanda Operator or Helm chart. endif::[]