• Glossary
  • Support
  • Downloads
  • DataStax Home
Get Live Help
Expand All
Collapse All

DataStax Project Mission Control

    • Overview
      • Release notes
      • FAQs
      • Get support
    • Installing DataStax Mission Control
      • Plan your install
      • Server-based Runtime Installer
        • Services setup with DataStax Mission Control Runtime Installer
      • Bring your own Kubernetes
        • Install Control Plane
        • Install Data Plane
    • Securing
      • Authentication
      • Connect LDAP authentication backend
      • Connect OpenID authentication backend
      • Client-to-node encryption
      • Internode encryption
      • Secure DataStax Mission Control
      • DSE Unified Authorization
    • Migrating
      • Migrate a DSE Cluster to DataStax Mission Control
    • Managing
      • Manage DSE clusters
        • Configure DSE
        • Cluster lifecycle
          • Create a cluster
          • Create a single-token cluster
          • Create a multi-token cluster
          • Changing cluster Replication Factor
          • Terminate a DSE cluster
          • Upgrade a DSE cluster
        • Datacenter lifecycle
          • Add a DSE datacenter
          • Terminate a DSE datacenter
        • Node lifecycle
          • Add DSE nodes
          • Terminate DSE nodes
          • Use per-node configurations
      • Manage DataStax Mission Control infrastructure
        • Manage projects
        • Manage clusters
        • Add a node to DataStax Mission Control clusters
        • Terminate a node from DataStax Mission Control clusters
        • Storage classes defined
      • Manage DataStax Mission Control resources
        • Access Admin Console
        • Configure DataStax Mission Control
        • Generate a support bundle
      • Observability
        • Metrics
    • Operations
      • Cleanup
      • Rebuild
      • Replace a node
      • Rolling restart
      • Upgrade SSTables
    • Reference
      • MissionControlCluster manifest
      • CassandraTask manifest
  • DataStax Project Mission Control
  • Installing DataStax Mission Control
  • Bring your own Kubernetes
  • Install Data Plane

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

DataStax Mission Control is currently in Public Preview. 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 join the Public Preview.

After meeting the prerequisites, run the steps in this topic:

  1. Validate Kubernetes cluster connectivity and version.

  2. Install DataStax Mission Control Admin Console.

  3. Access DataStax Mission Control Admin Console.

  4. Set configuration and install Data Plane.

Prerequisites

  • The kubectl CLI tool, v1.22 or later.

  • Managed 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. See Control Plane installation.

  • KOTS kubectl plugin installed with this command:

    `curl https://kots.io/install | bash`

    See kots documentation.

  • An installed Kubernetes cert-manager. To install, run one of the following commands:

    • kubectl command

    • Helm commands

    kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/v1.12.0/cert-manager.yaml
    helm repo add jetstack https://charts.jetstack.io
    helm repo update
    helm install \
      cert-manager jetstack/cert-manager \
      --namespace cert-manager \
      --create-namespace \
      --version v1.12.0 \
      --set installCRDs=true
  • DataStax Mission Control license file.

    Installation of DataStax Mission Control requires a license file containing installer coordinates and update streams. Generate a community edition license file at the DataStax Mission Control Public Preview Portal. If you need a replacement license file or a non-community edition please contact your account team.

Procedure

Validate Kubernetes cluster connectivity and version

  • Collect cluster information with the following command:

    • kubectl command

    • Sample result

    kubectl cluster-info
    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. When the command is successful, continue with validating the cluster version.

  • Validate the cluster version with the following command:

    • kubectl command

    • Sample result

    kubectl version --short
    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.

Install DataStax Mission Control Admin Console

Manage the DataStax Mission Control application through a browser-based administration console. This interface allows installation and upgrades of DataStax Mission Control along with 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 that has the kots plugin installed:

  • kubectl command

  • Sample result

kubectl kots install mission-control
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. Any namespace can host these components.

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.

Access 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.

Admin Console installer landing page

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.

License file upload prompt

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

Set configuration and install

DataStax Mission Control can 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 MissionControlCluster 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).

Initial configuration options

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 handles preflight checks, updates, and installation. After a few moments you should see the current version with a deployed status.

Admin Console dashboard DataStax Mission Control ready

You can now 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

Configure 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 MissionControlCluster Custom Resource utilizing this regional Data Plane cluster.

Install Control Plane Securing

General Inquiries: +1 (650) 389-6000 info@datastax.com

© DataStax | Privacy policy | Terms of use

DataStax, Titan, and TitanDB are registered trademarks of DataStax, Inc. and its subsidiaries in the United States and/or other countries.

Apache, Apache Cassandra, Cassandra, Apache Tomcat, Tomcat, Apache Lucene, Apache Solr, Apache Hadoop, Hadoop, Apache Pulsar, Pulsar, Apache Spark, Spark, Apache TinkerPop, TinkerPop, Apache Kafka and Kafka are either registered trademarks or trademarks of the Apache Software Foundation or its subsidiaries in Canada, the United States and/or other countries.

Kubernetes is the registered trademark of the Linux Foundation.

landing_page landingpage