From c199bd7d969bd4ee1e29bd26d7d6d0646d1413c0 Mon Sep 17 00:00:00 2001 From: JakeSCahill Date: Thu, 16 Jul 2026 16:42:04 +0100 Subject: [PATCH] docs: shadow linking troubleshooting only requires the flag on the shadow cluster The prerequisites already state that only the shadow cluster needs enable_shadow_linking, but the troubleshooting section told users to verify it on both clusters. LLM assistants latch onto this as a debugging gotcha even when irrelevant (DOC-2231). --- .../pages/kubernetes/shadowing/k-shadow-linking.adoc | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-) diff --git a/modules/manage/pages/kubernetes/shadowing/k-shadow-linking.adoc b/modules/manage/pages/kubernetes/shadowing/k-shadow-linking.adoc index cf6f3c3f49..33ea3daa4b 100644 --- a/modules/manage/pages/kubernetes/shadowing/k-shadow-linking.adoc +++ b/modules/manage/pages/kubernetes/shadowing/k-shadow-linking.adoc @@ -800,17 +800,16 @@ kubectl describe shadowlink --namespace Helm:: + -- -Verify shadow linking is enabled on both clusters: +Verify shadow linking is enabled on the shadow cluster: [,bash] ---- -kubectl exec --namespace --container redpanda -- \ - rpk cluster config get enable_shadow_linking - kubectl exec --namespace --container redpanda -- \ rpk cluster config get enable_shadow_linking ---- +Only the shadow (target) cluster requires the `enable_shadow_linking` property. The source cluster does not require it, unless that cluster also acts as the shadow cluster of another shadow link, such as in bi-directional topologies. + Check shadow link status for errors: [,bash]