Apache Cassandra stores application data across several servers rather than depending on one database machine. It can keep copies in different locations, making it useful for workloads whose capacity and availability requirements justify a distributed database. Applications must be designed around its query and consistency model: the choices about how data is arranged and how many copies answer a request. Kubernetes packaging does not make those database decisions for you.
Deployment and operating notes
Apache Cassandra remains a distributed database with its own version, Java, driver and operational requirements. This old directory page does not identify a supported current Kubernetes package. K8ssandra documents an operator-based option with related repair and backup components, but that is a packaging choice, not an Apache guarantee for every cluster configuration.
Start with application query patterns, consistency levels, replication and failure domains. Translate those into rack-aware placement, durable storage and capacity for compaction and repair. Kubernetes replicas are not a substitute for Cassandra replication, and deleting a pod is not the same as safely decommissioning a database node. For migration, capture schema, credentials, topology and client settings, then follow a supported server-version path with a tested backup restore. Verify reads and writes at the consistency levels the application actually uses. Retain a clear point after which writes must be reconciled before rollback; switching clients back to an older cluster can lose newly acknowledged data.
Historical upstream link check · 2026-10-09
The recorded upstream address responded successfully (HTTP 200) on 2026-10-09. GitHub confirms that helm/charts is archived: this is a historical chart distribution, not evidence that the application itself is retired. Link availability does not certify the historical installation instructions or current security support.
Website availability is separate from project, chart and image support. Use the current guidance and primary sources on this page to assess the distribution.
Historical Kubedex content
Preserved for context. Commands, versions, prices and results below reflect the original research.
The Apache Cassandra database is the right choice when you need scalability and high availability without compromising performance. Linear scalability and proven fault-tolerance on commodity hardware or cloud infrastructure make it the perfect platform for mission-critical data. Cassandra’s support for replicating across multiple datacenters is best-in-class, providing lower latency for your users and the peace of mind of knowing that you can survive regional outages.
Distributed
Every node in the cluster has the same role. There is no single point of failure. Data is distributed across the cluster
(so each node contains different data), but there is no master as every node can service any request.
Supports replication and multi-data center replication
Replication strategies are configurable.[15] Cassandra is designed as a distributed system, for the deployment of large numbers of nodes across multiple data centers. Key features of Cassandra’s distributed architecture are specifically tailored for multiple-data center deployment, for redundancy, for failover and disaster recovery.
Scalability
Designed to have read and write throughput both increase linearly as new machines are added, with the aim of no downtime
or interruption to applications.
Fault-tolerant
Data is automatically replicated to multiple nodes for fault-tolerance. Replication across multiple data centers is supported. Failed nodes can be replaced with no downtime.
Tunable consistency
Cassandra is typically classified as an AP system, meaning that availability and partition tolerance are generally
considered to be more important than consistency in Cassandra, Writes and reads offer a tunable level of consistency,
all the way from “writes never fail” to “block for all replicas to be readable”, with the quorum level in the middle.
MapReduce support
Cassandra has a Hadoop integration, with MapReduce support. There is support also for Apache Pig and Apache Hive.
Query language
Cassandra introduced the Cassandra Query Language (CQL). CQL is a simple interface for accessing Cassandra, as an
alternative to the traditional Structured Query Language (SQL).
Sources & further reading
Spotted something that needs another look?
Help improve this page →