Portworx is the cloud native storage company that enterprises depend on to reduce the cost and complexity of rapidly deploying containerized applications across multiple clouds and on-prem environments. With Portworx, you can manage any database or stateful service on any infrastructure using any container scheduler. You get a single data management layer for all of your stateful services, no matter where they run.
A popular Kubernetes persistent storage and Docker storage solution, Portworx is a clustered block storage solution and provides a Cloud-Native layer from which containerized stateful applications programmatically consume block, file and object storage services directly through the scheduler.
In this tutorial, you will learn how to deploy Cassandra to Kubernetes and use Portworx Volumes to provide HA capability:
- Use the Portworx Storage Class to create a PVC with 3 replicas of the data
- Use a simple YAML file to deploy Cassandra using this storage class
- How to validate data persistence by deleting the Cassandra pod
High Level Overview
First we will deploy Cassandra in a stateful set with only a single node (replicas=1) to show the basics of node failover. We will create some data, force Cassandra to flush the data to disk, and then failover the Cassandra pod and show how it comes back up with it's data intact.
Then, we're going to show how we can scale the cluster to 3 nodes and dynamically create volumes for each.
Other things you should know
To learn more about how why running Redis on Portworx is a great idea take a look at the following links:
- Guide to run [Cassandra in Docker] containers(https://portworx.com/use-case/cassandra-docker-container/)
- Guide to Kubernetes and Cassandra
- HA Cassandra on GKE
- HA Cassandrra on EKS
- HA Cassandra on AKS
- HA Cassandra on OpenShift
- Introduction to Portworx
- Customer Stories
- STORK open source project.
This scenario assumes you have already covered the following scenarios:

Steps
Cassandra Stateful Set on Portworx
Wait for Kubernetes & Portworx to be ready
First we need to wait for Kubernetes and Portworx to be ready. Be patient, this is not a very high performance environment, just a place to learn something :-
Step: Wait for Kubernetes to be ready
Click the below section which waits for all Kubernetes nodes to be ready.
watch kubectl get nodes
When all 4 nodes show status Running then hit clear
to ctrl-c and clear the screen.
Step: Wait for Portworx to be ready
Watch the Portworx pods and wait for them to be ready on all the nodes. This can take a few minutes since it involves pulling multiple docker images. You will see 'No resources found' until all images are pulled.
watch kubectl get pods -n kube-system -l name=portworx -o wide
When all the pods show STATUS Running and READY 1/1 then hit clear
to ctrl-c and clear the screen.
You can take a look at the cluster status using the pxctl command line tool:
PX_POD=$(kubectl get pods -l name=portworx -n kube-system -o jsonpath='{.items[0].metadata.name}')
kubectl exec -it $PX_POD -n kube-system -- /opt/pwx/bin/pxctl status
Now that we have the Portworx cluster up, let's proceed to the next step !