Skip to content

Commit

Permalink
Update docs/content/en/tasks/data-plane-registration/_index.md
Browse files Browse the repository at this point in the history
Co-authored-by: Alexander Dejanovski <[email protected]>
  • Loading branch information
Miles-Garnsey and adejanovski authored May 28, 2024
1 parent 04a27cb commit 89025e6
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion docs/content/en/tasks/data-plane-registration/_index.md
Original file line number Diff line number Diff line change
Expand Up @@ -24,4 +24,4 @@ A full list of options for this command can be found by using the `--help` flag.

#### Referencing a remote data plane within a K8ssandraCluster

Within the K8ssandraCluster DC list, the k8sContext can be used to reference a remote data plane. When creating ClientConfigs using k8ssandra-client, you will find that you can simply refer to the data plane using the name of the ClientConfig. However, if the ClientConfig has been created by hand, the ClientConfig contextName and meta.name may be different, in which case the contextName should be used. We recommend using k8ssandra-client to register data planes due to complexities like these.
Within the K8ssandraCluster DC list, the k8sContext can be used to reference a remote data plane. When creating ClientConfigs using k8ssandra-client, you will find that you can simply refer to the data plane using the name of the ClientConfig resource. However, if the ClientConfig has been created by hand, the ClientConfig `spec.contextName` and `meta.name` may be different, in which case the `spec.contextName` should be used. We recommend using k8ssandra-client to register data planes due to complexities like these.

0 comments on commit 89025e6

Please sign in to comment.