Install DataStax Mission Control with your own Kubernetes Cluster - Data Plane Mode

DataStax Mission Control is current in Private Preview. It is subject to the beta agreement executed between you and DataStax. DataStax Mission Control is not intended for production use, has not been certified for production workloads, and might contain bugs and other functional issues. There is no guarantee that DataStax Mission Control will ever become generally available. DataStax Mission Control is provided on an “AS IS” basis, without warranty or indemnity of any kind.

If you are interested in trying out DataStax Mission Control please contact your DataStax account team.

System requirements

kubectl v1.22 or higher
Kubernetes cluster(s):
- Amazon Elastic Kubernetes Service (EKS)
- Google Kubernetes Engine (GKE)
- Azure Kubernetes Service (AKS)
Kubeconfig file or context pointing to a Control Plane Kubernetes cluster
KOTS kubectl plugin downloaded:
```
`curl https://kots.io/install | bash`
```
getting started with kots cli
DataStax Mission Control license file. See License.

License

As part of your invitation to the DataStax Mission Control Private Preview you were provided with a license file as well as a URL for a dashboard to download all existing licenses attached to your account. In order to install DataStax Mission Control you MUST provide this license file. For help locating your license file please contact your account team.

Validate Kubernetes cluster connectivity and version

kubectl cluster-info

Sample Output:

Kubernetes control plane is running at https://WWW.XXX.YYY.ZZZ
KubeDNS is running at https://WWW.XXX.YYY.ZZZ/api/v1/namespaces/kube-system/services/kube-dns:dns/proxy
Metrics-server is running at https://WWW.XXX.YYY.ZZZ/api/v1/namespaces/kube-system/services/https:metrics-server:/proxy

Results display connection cluster information such as the Kubernetes control-plane URL and service addresses. If the command is successful then continue with validating the cluster version.

kubectl version --short

Sample output:

Client Version: v1.25.2
Kustomize Version: v4.5.7
Server Version: v1.22.12-gke.2300

The version sub-command of kubectl outputs version information for the kubectl CLI, embedded kustomize tooling, and the Kubernetes API server with which it is currently configured to communicate.

Installing DataStax Mission Control Admin Console

Management of the DataStax Mission Control application is handled through a browser-based Admin Console. This user interface allows the installation and upgrades of DataStax Mission Control along with the syncing of license file changes. The first step to installing DataStax Mission Control is the installation of this console onto your Kubernetes cluster. Run the following command from a terminal with an appropriately configured instance of kubectl with the kots plugin installed:

kubectl kots install mission-control

Sample output:

Enter the namespace to deploy to: mission-control
  • Deploying Admin Console
    • Creating namespace ✓
    • Waiting for datastore to be ready ✓
Enter a new password to be used for the Admin Console: ••••••••••
  • Waiting for Admin Console to be ready ✓

  • Press Ctrl+C to exit
  • Go to http://localhost:8800 to access the Admin Console

This process initially prompts you for the Kubernetes namespace where the management interface components should be deployed.

This value must be mission-control.

After the resources are installed the installer prompts for a password to be used for web-interface access. Type in your preferred value and record this value for use in an upcoming step.

With the Admin Console installed and available kubectl starts proxying access to the console. Visit http://localhost:8800 in your web browser to access the next step of the installation process.

Accessing DataStax Mission Control Admin Console

With your web browser open to the Admin Console interface you are now prompted for the password provided during installation of the Admin Console.

Type in this value and click Log In. You are now prompted to upload the license file.

Use the same license file that you used during Control Plane Mode installation.

Drag and drop your file into the upload box and click Upload license. A progress bar displays as DataStax Mission Control is downloaded and installed onto the Kubernetes cluster. Next you are prompted to configure DataStax Mission Control.

DataStax Mission Control release stream installing

Installation Configuration

DataStax Mission Control may be installed in one of two modes, Control Plane Mode or Data Plane Mode. In Control Plane Mode DataStax Mission Control is configured to monitor for creation and changes of DSECluster custom resources and to handle consolidation of cluster-level and datacenter-level resources.

While running in Control Plane Mode it is also possible to deploy Data Plane components (DSE nodes) within the local Kubernetes cluster. In Data Plane Mode DataStax Mission Control operators are configured to manage local Data Plane components (any component at the datacenter-level or below).

To install in Data Plane mode, uncheck the Control Plane box and click Install. You can change the configuration later if the wrong option is selected now. See modify configuration.

Admin Console dashboard DataStax Mission Control installing

The DataStax Mission Control Admin Console dashboard displays, indicating that the components are currently missing. This Admin Console handles installing the missing components with the configuration specified. After a few moments you should see the current version in deployed status.

Admin Console dashboard DataStax Mission Control ready

At this point you may safely press Ctrl+C in your terminal session where kubectl is running. This terminates the proxy connecting you to the Admin Console UI. To reconnect to this UI see Admin Console UI.

Configure this Data Plane cluster to communicate with the Control Plane

Configuring DataStax Mission Control

What’s next

With DataStax Mission Control installed in Data Plane Mode, proceed with one of the following options:

Configure the Data Plane cluster to communicate with the separate Control Plane Kubernetes cluster.
Create a DSE Cluster with kubectl and the DSECluster Custom Resource utilizing this regional Data Plane cluster.