Update docs/content/en/tasks/data-plane-registration/_index.md

Co-authored-by: Alexander Dejanovski <[email protected]>

docs/content/en/tasks/data-plane-registration/_index.md

@@ -13,7 +13,12 @@ Proceed with caution before deleting a ClientConfig or the secrets backing it. I
 #### Creating a ClientConfig and Kubeconfig secret
 Registering a data plane to a control plane can be error prone if done by hand. Instead use the `k8ssandra-client` CLI tool which can be found [here](https://github.com/k8ssandra/k8ssandra-client). It can be installed as a kubectl plugin by placing it on your `$PATH` or run completely separately.
 
-An example command to register a data plane to a control plane would be `./kubectl-k8ssandra register --source-context gke_k8ssandra_us-central1-c_registration-2 --dest-context gke_k8ssandra_us-central1-c_registration-1` where the source context (`gke_k8ssandra_us-central1-c_registration-2`) is the data plane (because that's the source of the credentials) and the destination context (`gke_k8ssandra_us-central1-c_registration-1`) is the control plane. 
+An example command to register a data plane to a control plane would be `kubectl k8ssandra register --source-context gke_k8ssandra_us-central1-c_registration-2 --dest-context gke_k8ssandra_us-central1-c_registration-1` where the source context (`gke_k8ssandra_us-central1-c_registration-2`) is the data plane (because that's the source of the credentials) and the destination context (`gke_k8ssandra_us-central1-c_registration-1`) is the control plane. 
+
+If the operator was installed in a different namespace than `k8ssandra-operator` in either the source or the destination cluster, use the following flags to indicate the actual namespaces:
+
+- `--dest-namespace <namespace>`
+- `--source-namespace <namespace>`
 
 A full list of options for this command can be found by using the `--help` flag.