Maintaining your Cassandra Operator cluster in Kubernetes

Maintain your Cassandra or DSE cluster in Kubernetes.

Follow these steps to perform Apache Cassandra® or DataStax Enterprise (DSE) maintenance tasks in Kubernetes.


If you have not yet created a Kubernetes cluster, see the tutorials on the site.
Tip: On the Kubernetes page, expand the left sidebar to navigate between the 6+ interactive tutorials.

This topic assumes you've completed the steps to configure the Cass Operator, and to provision and deploy Cassandra or DSE cluster in your existing Kubernetes environment.


  1. Backups
    DSE Backup and Restore Service (beta) enables cluster-wide backup and restore operations in Kubernetes. The features let you:
    • Create flexible local or cloud-based backup stores
    • Create backup configurations that enable you to schedule automatic keyspace backups at any frequency you require
    • Configure detailed backup retention policies depending on your needs
    • Handle all backup tasks from a single node using a simple set of CQL commands
    • Flexibly restore backups to a current cluster as well as new clusters, at the keyspace or table level
    For details about using the features in Kubernetes, start in the topic About the DSE Backup and Restore Service (beta).
  2. Repairs

    Cass Operator does not automate the process of performing traditional repairs on keyspace ranges where the data has become inconsistent due to a Cassandra or DSE instance becoming unavailable.

    DSE provides NodeSync, a continuous background repair service that is declarative and self-orchestrating. After deploying the DSE cluster in your Kubernetes environment, use NodeSync enable options on all new tables.