Getting started with Cassandra Operator

Getting started with Cass Operator in Kubernetes.

To get started, follow the steps in this topic.

Quick start

Run these commands:
kubectl create -f
# *** The next command is for Google Kubernetes Engine (GKE). Adjust based on your cloud or storage options.
kubectl create -f
kubectl -n cass-operator create -f

Load the operator

Apply the provided manifest.
Note: Because the manifest install a Custom Resource Definition (CRD), the user running the command needs cluster-admin privileges.
kubectl apply -f
Because this manifest installs a Custom Resource Definition, the user running the above command must have cluster-admin privileges. The command above deploys the operator, along with any requisite resources such as Role and RoleBinding to the cass-operator namespace.
To check whether the operator is ready and in a Running state:
kubectl -n cass-operator get pods --selector name=cass-operator
NAME                             READY   STATUS    RESTARTS   AGE
cass-operator-555577b9f8-zgx6j   1/1     Running   0          25h

Loading the operator via Helm (optional)

Optionally, you can use Helm to load the Cass Operator. First, create the destination namespace:
kubectl create namespace my-custom-namespace
Then load the operator. Example:
helm install --namespace=my-custom-namespace cass-operator ./charts/cass-operator-chart
Optionally, you can override the following default Helm values:
serviceAccountName: cass-operator
clusterRoleName: cass-operator-cluster-role
clusterRoleBindingName: cass-operator
roleName: cass-operator
roleBindingName: cass-operator
deploymentName: cass-operator
deploymentReplicas: 1
image: "datastax/cass-operator:1.1.0"
imagePullPolicy: IfNotPresent
Note: Helm does not install a storage-class for the Cassandra pods. For help with that requirement, see the next section.

Create and apply a StorageClass

Create an appropriate StorageClass, which will define the type of storage to use for Cassandra nodes in a cluster. For example, here is a StorageClass for using SSDs in GKE. This YAML is available at operator/deploy/k8s-flavors/gke/storage.yaml.
kind: StorageClass
  name: server-storage
  type: pd-ssd
  replication-type: none
volumeBindingMode: WaitForFirstConsumer
reclaimPolicy: Delete
Apply the StorageClass YAML:
kubectl apply -f

Create and apply a CassandraDatacenter

The following resource defines a Cassandra 3.11.6 datacenter with three nodes on one rack. This YAML is available at operator/example-cassdc-yaml/cassandra-3.11.6/example-cassdc-minimal.yaml.
kind: CassandraDatacenter
  name: dc1
  clusterName: cluster1
  serverType: cassandra
  serverVersion: 3.11.6
    insecure: {}
  size: 3
      storageClassName: server-storage
      - ReadWriteOnce
          storage: 5Gi
      authenticator: org.apache.cassandra.auth.PasswordAuthenticator
      authorizer: org.apache.cassandra.auth.CassandraAuthorizer
      role_manager: org.apache.cassandra.auth.CassandraRoleManager
      initial_heap_size: 800M
      max_heap_size: 800M
Apply the CassandraDatacenter YAML:
kubectl -n cass-operator apply -f

Verify status

To check the status of pods in the Cassandra cluster:
kubectl -n cass-operator get pods --selector
NAME                    READY   STATUS    RESTARTS   AGE
cluster1-dc1-r1-sts-0   2/2     Running   0          26h
cluster1-dc1-r1-sts-1   2/2     Running   0          26h
cluster1-dc1-r1-sts-2   2/2     Running   0          26h 
To see the current progress of bringing the Cassandra datacenter online, check the cassandraOperatorProgress field of the CassandraDatacenter's status sub-resource:
kubectl -n cass-operator get cassdc/dc1 -o "jsonpath={.status.cassandraOperatorProgress}"
Note: cassdc and cassdcs are supported short forms of CassandraDatacenter.

A value of Ready, as shown above, means the operator has finished setting up the Cassandra datacenter.

You can also check the Cassandra cluster status using nodetool by invoking it on one of the pods in the cluster:
kubectl -n cass-operator exec -it -c cassandra cluster1-dc1-r1-sts-0 -- nodetool status
Datacenter: dc1
|/ State=Normal/Leaving/Joining/Moving/Stopped
--  Address         Load       Tokens       Owns (effective)  Host ID                               Rack
UN  224.82 KiB  1            65.4%             5e29b4c9-aa69-4d53-97f9-a3e26115e625  r1
UN    186.48 KiB  1            61.6%             b119eae5-2ff4-4b06-b20b-c492474e59a6  r1
UN    205.1 KiB   1            73.1%             0a96e814-dcf6-48b9-a2ca-663686c8a495  r1 

What's next?