Choose an installation method

Select the Mission Control installation method that meets your organization’s needs based on your environment, use case, and deployment requirements.

Follow these steps to select your installation path:

  1. Review the installation requirements.

  2. Choose your installation environment:

    • Bare-metal or VM: Install Mission Control directly on physical or virtual machines when you don’t have Kubernetes

    • Existing Kubernetes cluster: Integrate Mission Control into your existing Kubernetes infrastructure

  3. Choose your installation method:

    • KOTS: Use this method for guided installation with default configurations and automated upgrades

    • Helm: Use this method for fine-grained control and GitOps workflow integration

    • OpenShift: Use this method when you run Red Hat OpenShift as your Kubernetes distribution

  4. Consider the following deployment factors:

    • Single vs multiple instances: Choose based on your availability and scalability requirements

    • Online vs offline installation: Choose based on your network connectivity and security requirements

    • Single vs multiple regions: Choose based on your geographic distribution and performance requirements

Compare installation environments

Choose your installation environment from these options:

Installation environment Use case Advantages Disadvantages

Bare-metal or VM

Install Mission Control directly on physical or virtual machines when you don’t have Kubernetes

  • Bundles all necessary components for deployment

  • No external Kubernetes cluster required

  • Simpler initial setup

  • Less flexibility for scaling and workload management

  • Limited integration with Kubernetes ecosystem

Your existing Kubernetes cluster

Integrate Mission Control into your existing Kubernetes infrastructure

  • Leverages Kubernetes' scalability, flexibility, and ecosystem

  • Supports advanced Kubernetes features

  • Better integration with existing infrastructure

  • Requires Kubernetes knowledge for cluster management and maintenance

  • Additional capacity planning required

Compare installation methods

Choose your installation method from these options:

Installation method Use case Advantages Disadvantages

KOTS

Use this method for guided installation with default configurations and automated upgrades.

  • Simplifies installation and configuration.

  • Provides a guided setup process.

  • Supports automated upgrades.

  • Includes a web-based management interface.

  • Limited customization compared to Helm.

  • Less flexibility for advanced configurations.

  • Web interface required for management.

Helm

Use this method for fine-grained control and GitOps workflow integration.

  • Highly customizable using Helm values.

  • Supports automated upgrades.

  • Integrates with GitOps workflows.

  • CLI-based management.

  • Requires familiarity with Helm and Kubernetes configuration management.

  • More complex initial setup.

  • Manual configuration required.

OpenShift

Use this method when you run Red Hat OpenShift as your Kubernetes distribution.

  • Benefits from OpenShift’s security features and enterprise capabilities.

  • Seamless integration with OpenShift ecosystem.

  • Enhanced security and compliance features.

  • Limited to OpenShift environments.

  • Reduced portability to other Kubernetes distributions.

  • OpenShift-specific knowledge required.

Deployment considerations

Choose these deployment factors based on your requirements:

Single vs multiple instances

Deployment type Use case Advantages Disadvantages

Single Instance

Use this option for development or testing only. Production environments require a minimum of three nodes.

  • Simpler setup and management.

  • Requires fewer resources.

  • Lower operational complexity.

  • No built-in redundancy or failover.

  • Limited scalability.

  • Single point of failure.

Multiple Instances

Use this option for high-availability and production-grade deployments.

  • Ensures failover and reliability.

  • Supports horizontal scaling for workload distribution.

  • Better resource utilization.

  • Requires more infrastructure and management.

  • Increased complexity in configuration and maintenance.

  • Higher operational overhead.

Online vs offline installation

Installation type Use case Advantages Disadvantages

Online

Use this method when you have internet access and want to simplify the installation process.

  • Simplifies installation and updates.

  • Supports automated upgrades.

  • Access to latest features and fixes.

  • Requires internet access for installation and updates.

  • External dependencies for package downloads.

  • Potential security concerns.

Offline Airgap

Use this method when you operate in a secure or isolated environment without internet access.

  • Enables deployment in highly secure environments.

  • No external dependencies after initial setup.

  • Better control over updates.

  • Requires manual updates and package transfers.

  • More effort needed for installation and maintenance.

  • Delayed access to updates.

Regional deployment

Deployment regions Use case Advantages Disadvantages

One region

Use this option when you operate in a single geographic location.

  • Centralized management and monitoring.

  • Shared resources for all users.

  • Simpler configuration.

  • Limited to a single region.

  • Shared resources may impact performance.

  • No geographic redundancy.

Multiple regions

Use this option when you need to serve multiple geographic locations.

  • Isolated management and monitoring.

  • Dedicated resources for each group.

  • Geographic redundancy.

  • Increased complexity in configuration and management.

  • Requires additional resources for each region.

  • Higher operational overhead.

Next steps

First, prepare your bare metal/VM or existing cluster. After your installation environment is prepared, then you can follow the installation guide for your chosen installation method: KOTS, Helm, or OpenShift.

Was this helpful?

Give Feedback

How can we improve the documentation?

© 2025 DataStax | Privacy policy | Terms of use | Manage Privacy Choices

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.

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