Quickstart for Kubernetes Operator for Apache Cassandra

Run this kubectl command to reference a YAML file that applies the Kubernetes Operator for Apache Cassandra manifest’s definitions to the connected Kubernetes cluster.

kubectl create -f https://raw.githubusercontent.com/k8ssandra/cass-operator/v1.7.1/docs/user/cass-operator-manifests.yaml

Run the following kubectl command to apply a YAML manifest that defines the storage settings to use for Cassandra nodes in a cluster. An example is SSD as a storage type. In this case, storage settings are for a GKE cluster. Kubernetes uses the StorageClass resource as an abstraction layer between pods needing persistent storage and the physical storage resources that a specific Kubernetes cluster can provide.

kubectl create -f https://raw.githubusercontent.com/k8ssandra/cass-operator/v1.7.1/operator/k8s-flavors/gke/storage.yaml

Finally, run the following kubectl command to apply a YAML manifest that defines a CassandraDatacenter with the open-source Apache Cassandra 3.11.7 image with three nodes on one rack in the Kubernetes cluster.

kubectl -n cass-operator create -f https://raw.githubusercontent.com/k8ssandra/cass-operator/v1.7.1/operator/example-cassdc-yaml/cassandra-3.11.x/example-cassdc-minimal.yaml

kubectl -n cass-operator create -f https://raw.githubusercontent.com/k8ssandra/cass-operator/master/operator/example-cassdc-yaml/dse-6.8.x/example-cassdc-minimal.yaml

Navigate to the Kubernetes Engine page in Cloud Console, and log into your account.

If you have not already done so, select your project.

On the Clusters tab, click the link for your cluster’s name.

Navigate through the Details, Storage, and Nodes sections to familiarize yourself with the created resources.

Click Workloads.

Click the Cluster link on the Workloads page to load details about the Kubernetes Operator for Apache Cassandra and Cassandra deployments in the Kubernetes cluster.

Select Services & Ingress to see how the Service labels for the deployed cluster1 Cassandra cluster and for the dc1 datacenter correspond to the YAML manifest applied using kubectl earlier. Notice the three serving pods. Services are sets of pods with a network endpoint that can be used for discovery and load balancing. Ingresses are collections of rules for routing external HTTP or HTTPS traffic to Services. From the initial Services tab, click the cluster1-dc1-service to get that service’s status.

For more details, scroll to the Serving pods section, and select the link for one of the serving pods. The Cloud Console switches to the Workloads tab, and the Pod details page includes the status labels, such as cassandra.datastax.com/node-state: Started and additional metadata. Scroll down to the Containers section and notice the running container for the cassandra 3.11.7 image. This container is deployed to your Kubernetes cluster and matches the YAML configuration applied earlier in this topic.