From dcc061dd0c386db6ff67ff93a68c7fc3bd2d1a97 Mon Sep 17 00:00:00 2001 From: JakeSCahill Date: Wed, 15 Jul 2026 13:09:41 +0100 Subject: [PATCH] docs: state minimum operator version for cross-namespace clusterRef The namespace field on clusterRef exists from operator 26.2.1-beta.3. On earlier 26.2 betas, Kubernetes silently prunes the unknown CRD field and the reference resolves in the ShadowLink's namespace, which is a quiet misconfiguration. Follow-up to #1793 review. --- modules/manage/pages/kubernetes/shadowing/k-shadow-linking.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/modules/manage/pages/kubernetes/shadowing/k-shadow-linking.adoc b/modules/manage/pages/kubernetes/shadowing/k-shadow-linking.adoc index 589d5e8fe0..f7c14b592d 100644 --- a/modules/manage/pages/kubernetes/shadowing/k-shadow-linking.adoc +++ b/modules/manage/pages/kubernetes/shadowing/k-shadow-linking.adoc @@ -73,7 +73,7 @@ The operator automatically resolves cluster connection details from the referenc When using `clusterRef`, the operator handles authentication automatically using the cluster's internal credentials. For clusters that are not managed by the same operator, use `staticConfiguration` instead. ==== + -By default, a `clusterRef` resolves in the same namespace as the `ShadowLink` resource. If the source and shadow clusters are managed by the same operator but deployed in different namespaces on the same Kubernetes cluster, set the `namespace` field on the source cluster's `clusterRef`: +By default, a `clusterRef` resolves in the same namespace as the `ShadowLink` resource. If the source and shadow clusters are managed by the same operator but deployed in different namespaces on the same Kubernetes cluster, set the `namespace` field on the source cluster's `clusterRef`. The `namespace` field requires Redpanda Operator 26.2.1-beta.3 or later; on earlier versions, the field is silently ignored and the reference resolves in the ShadowLink's namespace. + .`shadowlink.yaml` [,yaml]