k8ssandra-operator

K8ssandra-operator is a Kubernetes operator that deploys and manages Apache Cassandra and DataStax Enterprise (K8ssandra) clusters.

  • Backup
  • Databases
  • Tools & Utilities
K8ssandra-operator is a Kubernetes operator that deploys and manages Apache Cassandra and DataStax Enterprise (K8ssandra) clusters. It automates scaling, backups, repairs, and upgrades so self-hosters can run a distributed NoSQL database on their own Kubernetes cluster without needing deep Cassandra expertise.

Platform availability

Available on 0 of 10 platforms

  • Unraid (not listed)
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

53/100 Fair

Maintained
100last commit 4 days ago
Popular
48244 GitHub stars
Easy to install
250 install platforms, install notes, Docker image
Light to run
208 GB minimum RAM, runs on ARM
Security check
201 serious finding, 3 minor, CI, tests, OpenSSF Scorecard 4.2/10
GitHub stars
244
Open issues
447
Last commit
2026-11-17
Latest release
v1.34.0
License
Apache-2.0
Activity
rising

Checked 3 days ago - source: GitHub (k8ssandra/k8ssandra-operator)

Resources & Compatibility

Minimum requirements: 8 GB RAM, 4 CPU core(s). ARM (e.g. Raspberry Pi) is supported.

Checked 54 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Create a local Kind cluster first If you're installing on your own machine, run ./setup-kind-multicluster.sh --kind-worker-nodes 4 to create a small local Kubernetes cluster made with Docker called Kind. Without a running cluster, kubectl and the K8ssandra operator installation have nowhere to run. source
  • Expected kind-registry error When the local single-cluster setup script finishes, it may show an error saying the kind-registry endpoint (a helper for local container images) already exists in network kind. That message is expected if that Docker network is already there, so you can continue using the generated kubeconfig file. source
  • Medusa S3 backup secret If you want Medusa to back up to S3, apply a Kubernetes Secret (a saved config for sensitive values) named medusa-bucket-key with the exact key medusa_s3_credentials and your real access key values before installing/upgrading K8ssandra or starting a backup. If the key name is wrong or the values are placeholders, Medusa can't reach the backup bucket. source

Fetched 53 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

How can I test K8ssandra Operator on my own machine?

Create a local Kind cluster first, for example with the provided script and four Kind worker nodes. kubectl and the operator need a running Kubernetes cluster.

Is the kind-registry error during local setup a problem?

The kind-registry endpoint already exists message is expected if that Docker network is already present. You can continue using the generated kubeconfig file.

What secret must exist for Medusa to back up to S3?

Apply a Kubernetes Secret named medusa-bucket-key with the exact key medusa_s3_credentials and real access key values before installing, upgrading, or starting a backup. Wrong key names or placeholder values prevent Medusa from reaching the bucket.

Where should I start when a K8ssandra cluster deployment is failing?

Check the K8ssandra cluster status first. It reports useful information about components such as CassandraDatacenter, Stargate, and Reaper.

Does the operator require multiple Kubernetes clusters or regions?

The operator supports multi-cluster and multi-region Cassandra deployments. It also works in single-cluster and single-region Kubernetes environments.

Answers sourced from docs.k8ssandra.io, docs.k8ssandra.io, github.com, github.com, github.com

Community

Collected 48 days ago - public community threads