A Kubernetes operator for automating Apache Cassandra cluster management and operations on Kubernetes platforms.
Cassandra Operator is a Kubernetes operator that manages Apache Cassandra clusters on Kubernetes platforms. It automates operational tasks like deployment, scaling, and maintenance by treating Cassandra clusters as Kubernetes custom resources. The project simplifies running stateful Cassandra workloads in containerized environments.
DevOps engineers and platform teams who need to run Apache Cassandra on Kubernetes infrastructure. It's particularly useful for organizations adopting cloud-native architectures with stateful databases.
Developers choose this operator because it provides Kubernetes-native management for Cassandra, reducing operational complexity through automation. It enables teams to manage Cassandra clusters using familiar Kubernetes tools and patterns rather than manual administration.
Kubernetes operator for Apache Cassandra
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Automates operational tasks like scaling, maintenance, and recovery by treating Cassandra clusters as Kubernetes custom resources, simplifying database administration.
Uses Kubernetes APIs and custom resources for declarative management, aligning with cloud-native practices and enabling GitOps workflows.
Supports specific Cassandra versions 3.11.9 and 4.0.0, providing flexibility for different application needs, as stated in the README.
Includes Helm charts for easier deployment and management on Kubernetes, reducing setup complexity for teams familiar with Helm.
The operator is no longer supported, as explicitly noted in the README, making it unsuitable for production use or new deployments.
The README warns that breaking changes are frequent and some features are incomplete, leading to potential instability and compatibility issues.
With the project sunset, there is no active maintenance, bug fixes, or community support, limiting long-term viability and troubleshooting.
Requires Kubernetes 1.15+ and Helm 3, which may not be available in all environments, adding to setup overhead and limiting flexibility.