Configure a data plane to communicate with the control plane
As your system’s lifecycle changes and you create or terminate clusters and datacenters, adjust the data plane installation accordingly. When you install a cluster in data plane mode, you must configure it to communicate with an independent cluster that functions as the control plane.
Prerequisites
-
You have the Mission Control CLI,
mcctl. -
You can access your clusters with
kubectl. -
The default
kubeconfiglocated at~/.kube/configprovides access to all control and data plane clusters. -
Mission Control is installed in each cluster in the
mission-controlnamespace.
Configure data plane updates
In this example, there are three Kubernetes clusters named control, east, and west.
Configure the control plane cluster to give it access to the east and west clusters.
-
Use
mcctlto register the data plane to the control plane:shellmcctl register --source-context EAST --dest-context CONTROLReplace the following:
-
EAST: The context of the data plane cluster -
CONTROL: The context of the control plane clusterAfter you register a data plane, the Mission Control control plane immediately recognizes it. This allows you to manage resources across the two planes.
-
-
Optional: Check the
clientconfigandsecretresources in the mission-control namespace to validate the connection between the control plane and data plane.-
Check the
clientconfigresource for the registered data plane:shellkubectl get -n mission-control clientconfigResult
The system returns a list of registered data planes.
NAME AGE EAST 392d -
Check the
secretresource for the registered data plane:shellkubectl get -n mission-control secretResult
The system returns a list of registered data planes.
NAME TYPE DATA AGE EAST-config Opaque 1 392dYou can also verify the data plane context registration in the Mission Control UI. Check the Data Plane Context field in the cluster creation and modification forms.
-
-
Repeat steps 1 and 2 for the
westcluster.
