Upgrade Cassandra Operator and related resources in Kubernetes

Steps to upgrade Cass Operator and related resources in Kubernetes.

Follow the steps in this topic to upgrade the Cass Operator and related resources in Kubernetes.

Cass Operator upgrades

To upgrade an existing Cassandra or DSE cluster in Kubernetes from a prior Cass Operator release to v1.3.0, apply the latest Cass Operator v1.3.0 manifest YAML.

During the upgrade, Cass Operator preserves previously defined values such as the namespace (example: cass-operator), the resource type (example: cassdc), and the datacenter name (example: dc1) plus other default or customized settings specified in the prior release's YAML.

To apply the latest Cass Operator manifest YAML – on a local machine where you've already established a connection with a Kubernetes project and cluster – use a kubectl command. Example:
kubectl apply -n cass-operator -f https://raw.githubusercontent.com/datastax/cass-operator/v1.3.0/docs/user/cass-operator-manifests-v1.16.yaml
Cass Operator returns a summary about the updates. Example:
namespace/cass-operator unchanged
serviceaccount/cass-operator unchanged
secret/cass-operator-webhook-config configured
customresourcedefinition.apiextensions.k8s.io/cassandradatacenters.cassandra.datastax.com unchanged
clusterrole.rbac.authorization.k8s.io/cass-operator-cluster-role configured
clusterrolebinding.rbac.authorization.k8s.io/cass-operator unchanged
role.rbac.authorization.k8s.io/cass-operator unchanged
rolebinding.rbac.authorization.k8s.io/cass-operator unchanged
service/cassandradatacenter-webhook-service unchanged
deployment.apps/cass-operator configured
validatingwebhookconfiguration.admissionregistration.k8s.io/cassandradatacenter-webhook-registration unchanged
Tip: For information about establishing a connection from a local machine to a Kubernetes cluster, so that you can subsequently run kubectl commands that are directed to resources in the cluster, see Create a Kubernetes cluster.

In the case of an upgrade from a prior release to Cass Operator v1.3.0, it is generally not necessary to reapply the two sets of YAML files that defined the storage class and CassandraDatacenter (unchanged since 1.2.0). Apply only the v1.3.0 manifest YAML as shown above. For information about all three sets of YAML definitions provided by Cass Operator, see Get started with Cassandra Operator.

By applying the Cass Operator v1.3.0 manifest, you can then update configuration YAML to enable newly supported features. For example, Cass Operator v1.3.0 added support for Cassandra Reaper, which is a repair tool for Cassandra clusters. See Repair Cassandra clusters in Kubernetes.

What's next?

To upgrade Cassandra or DSE cluster settings in Kubernetes, using options such as forceUpgradeRacks, see the next topic.