What is Cassandra Operator?

Cass Operator automates deploying and managing Cassandra or DSE in Kubernetes.

DataStax Kubernetes Operator for Apache Cassandra® (Cass Operator) automates the process of deploying and managing open-source Apache Cassandra® or DataStax Enterprise (DSE) in a Kubernetes cluster.

Cass Operator distills the user-supplied information down to the number of nodes and cluster name to manage the lifecycle of individual Kubernetes resources. Additional options are available, but for starters, that's essentially all you'll need to specify. Now the process of managing the distributed Cassandra or DSE data platform is turnkey and much easier, which means your team is free to focus on the application layer and its functionality.

You can configure and use Cass Operator with any of the following certified Kubernetes platforms:
  • Open-source Kubernetes
  • Google Kubernetes Engine (GKE)
  • Pivotal Container Service (PKS)

Let's start by looking at containers and the emergence of Kubernetes as the premier platform for application orchestration.

Optimizing data management in containers with Kubernetes

Containers have become an increasingly popular technology that are used to accelerate today's application development. Thanks to prevalent container platforms like Docker, you can package applications much more efficiently compared with virtual machines. With containers, apps and all of their dependencies are packaged together into a minimal deployable image. This approach helps DevOps teams avoid the notorius "well, it works on my machine" problem where apps on developer workstations differ from those that are deployed.

The benefits of containers extend beyond simply speeding up development. As a developer, you can use containers to move applications between environments and guarantee that your apps behave as expected. You can improve the speed of delivery and ship better software, at scale, faster. Instead of provisioning new virtual machines for each instance of an application, multiple containers can be executed on the same hardware to reduce costs.

This functionality all seems ideal, but how are you and your team going to assign containers to servers? Who will manage configuring the load balancers and network rules? These concerns led to the creation of container orchestration platforms. The leader in this space is Kubernetes.

Highlighting just a few of the advantages:
  • Kubernetes accepts definitions for services and handles the assignment of containers to servers and connecting them together.
  • Kubernetes dynamically tracks the health of the running containers. If a container goes down, Kubernetes handles restarting it, and can schedule its container replacement on other hardware.
  • By using Kubernetes to orchestrate containers, you can rapidly build microservice-powered applications and ensure they run as designed across any Kubernetes platform.

Cassandra and DSE in Kubernetes clusters

Cassandra and DSE substantially simplify development. All nodes are equal, and each node is capable of handling read and write requests, and no single point of failure exists. Data is automatically replicated between failure zones to prevent the loss of a single container taking down your application. With simple configuration options in Cass Operator, Cassandra and DSE databases can rapidly take advantage of Kubernetes orchestration and are well suited for the container-first approach in your enterprise.

Ready to get started?

Start by reading the release notes.

If you have questions, refer to the FAQs.

Then follow the steps to get started with Cass Operator in a Kubernetes cluster.