Mission Control release notes

DataStax provides the Mission Control Platform with a collection of tools, operators, and interfaces for the next generation of Hyper-Converged Database (HCD), DataStax Enterprise (DSE), and Apache Cassandra® management on the public cloud, on-premises, or hybrid environments.

Mission Control components include tools to install Mission Control and manage clusters.

Here are the features, enhancements, and updates per Mission Control version.

Version 1.9.0

Released on April 14, 2025, this version includes the following items:

New features and enhancements

This version extends encryption certificates duration to a default of 20 years to prevent outages caused by expired certificates. (MC-1650)

Certificate and certificate authority (CA) expiration durations are now configurable with the Certificate resource.

You must perform the following post-upgrade steps to rotate the CA and each node’s certificate in a rolling fashion for all existing DSE clusters.

Retrieve your cluster’s base-64-encoded superuser name and password:

DBUSER=$(kubectl get secret -n PROJECT_NAMESPACE CLUSTER_NAME-superuser -o jsonpath='{.data.username}' | base64 --decode | xargs)
DBPASS=$(kubectl get secret -n PROJECT_NAMESPACE CLUSTER_NAME-superuser -o jsonpath='{.data.password}' | base64 --decode | xargs)

Replace the following:

PROJECT_NAMESPACE: The namespace where your DSE cluster is deployed.
CLUSTER_NAME: The name of your DSE cluster

Reload the truststore in all DSE pods to ensure the latest CA is trusted:

for i in kubectl get po -l app.kubernetes.io/name=cassandra -n PROJECT_NAMESPACE | grep sts | awk '{print $1}'; do echo $i; kubectl exec $i -n PROJECT_NAMESPACE -c cassandra -- dsetool -a $DBUSER -b $DBPASS tsreload server; done

Perform a rolling restart on the cluster.

In the Mission Control UI, select your project, and then select your cluster.
On the Clusters overview page, click Bulk Actions.

Click Restart, and then click Run.

This ensures all nodes use refreshed certificates with the new CA.

Recovery procedure for expired certificates

If nodes fail to restart due to certificates that have already expired, use the following procedure to force the restart.

This procedure is a workaround for expired certificates and will cause downtime for your cluster. You should only use this procedure if the cluster fails to restart due to expired certificates.

MissionControlCluster spec
UI simple mode

Set the Stopped field to true to stop the cluster:

...
    Cassandra:
      Datacenters:
        Dse Workloads:
        Metadata:
          Name:  dc1
          Pods:
          Services:
            Additional Seed Service:
            All Pods Service:
            Dc Service:
            Node Port Service:
            Seed Service:
        Per Node Config Init Container Image:
        Per Node Config Map Ref:
        Racks:
          Name:   rack1
        Size:     3
        Stopped:  true
...

Submit the updated MissionControlCluster YAML file to Kubernetes:
```
kubectl apply -f MISSION_CONTROL_CLUSTER_FILE.yaml
```
Replace MISSION_CONTROL_CLUSTER_FILE.yaml with the name of your MissionControlCluster YAML file.
Wait for all pods to stop.
In the Mission Control UI, select your project, and then select your cluster.
Click Bulk Actions.
Select Rotate Internode Certificates from the Action type list, and then click Run.
Revert the change from step 1, and wait for Mission Control to recreate the pods.

In the Mission Control UI, select your project, and then select your cluster.
Click Modify Cluster.
In the Topology section, under Datacenter, toggle the Stop this DC switch to on.
Click Modify Cluster.
Wait for all pods to stop.
Go back to Clusters overview page, and then click Bulk Actions.
Select Rotate Internode Certificates from the Action type list, and then click Run.
Go back to Clusters overview page, and then click Modify Cluster.
In the Topology section, under Datacenter, toggle the Stop this DC switch to off.
Click Modify Cluster.
Wait for Mission Control to recreate the pods.

The cqlsh pod now uses the same service account as the one that deploys the target instead of the default service account. (MC-1609)

This change improves compatibility with environments that enforce stricter security policies and enhances deployment reliability.
Updated HCD images to use UBI versions. (MC-1663)
Added a REST API endpoint for rotating out internode leaf certificates manually. (MC-1646)
Introduced support for overriding the imageConfig in the Mission Control default Helm values.yaml file. (MC-1639)

This feature lets you upgrade the k8ssandra-client to v0.6.3 while applying bug and CVE fixes without requiring a cass-operator upgrade.
Replaced the bitnami/kubectl image with the k8ssandra-client image for the crdPatcherJob, ensuring the latest base image build for kubectl. (MC-1633)
Replicated releases are now generated using channel IDs instead of project names or slugs. (MC-1615)
Renamed yq image references to perNodeConfig image references and removed the yq container. (MC-1606)

Security updates

Removed the functionality that automatically created a default Dex user during installation to enhance security. (MC-1484)

If you previously installed Mission Control with a default user, you must change the Dex user’s password or delete the user entirely.

You must now edit the configuration before deployment to manually set the admin user password. Preflight checks will fail if the password is not set.

This change helps prevent unauthorized access and improves the overall security of your Mission Control installation.

Upgraded the k8s-sidecar container in Loki to v1.30.3. (MC-1578)
Updated the Loki nginx container to v1.27-alpine to resolve security vulnerabilities. (MC-1634)
Upgraded Gin to v1.10.0 and golang.org/x/net to v0.38.0 to resolve security vulnerabilities. (MC-1643)
Updated the following charts to address CVEs: (MC-1388)
- Loki to v5.41.4
- Mimir-distributed to v5.1.4
- Grafana to v6.48.0
- kube-state-metrics to v5.30.1
- Dex to v2.42.0
Upgraded the data-api image to v1.0.24 to address critical vulnerabilities. (MC-1577)

Mission Control release notes

Version 1.0.0-beta.3

New features and enhancements

Security updates

Fixed issues

Version 1.0.0-beta.2

Fixed issues

Version 1.0.0-beta.1

New features and enhancements

Security updates

Fixed issues

Version 0.8.0

New features and enhancements

Security updates

Version 0.7.1

New features and enhancements

Security updates

Fixed issues

Version 0.7.0

New features and enhancements

Security fixes

Fixed issues

Version 0.6.0

New features and enhancements

Security updates

Fixed issues

Version 0.5.0

Security updates

New features and enhancements

Fixed issues

Version 0.4.0

New features and enhancements

Fixed issues

Version 0.3.0

Security updates

New features and enhancements

Version 0.2.0

New features and enhancements

Version 0.1.0

Installation

Lifecycle Management

Was this helpful?