Mission Control clusters are objects describing the topology and settings of Hyper-Converged Database (HCD), DataStax Enterprise (DSE), and Apache Cassandra® database instances.

Mission Control creates at least one project to contain a logical group of database clusters.

Database cluster management encompasses the entire lifecycle of cluster components. This includes creating datacenter-level resources across Kubernetes cluster boundaries, orchestrating automation steps at appropriate intervals given a specific cluster state, and remediating issues as they arise. Given the distributed nature of Mission Control, there are Kubernetes operators local to each Kubernetes cluster which respond to events within the local cluster. This enables continuous operations and remediation even during periods of network partitioning.

Use Mission Control for database cluster tasks such as configuration, execution, and monitoring status during a cluster lifecycle or a:

Interactions with Mission Control are broadly categorized as declarative or imperative. Use declarative APIs to define a desired end-state, and then Mission Control constantly takes steps to achieve that declared goal. For example, you would define a DataStax Enterprise (DSE) or Hyper-Converged Database (HCD) cluster or datacenter through declarative APIs because these are long-lived resources. In comparison, imperative APIs describe a singular operation or task to be run to completion with an associated status. Imperative APIs within Mission Control include operational tasks on a specified cluster, such as performing a rolling restart.

Perform declarative or imperative operations at either the cluster or the datacenter level.