New to KubeDB? Please start here.

Cassandra Update Version Overview

This guide will give you an overview on how KubeDB Ops-manager operator update the version of Cassandra.

Before You Begin

• You should be familiar with the following KubeDB concepts:
  • Cassandra
  • CassandraOpsRequest

How update version Process Works

The following diagram shows how KubeDB Ops-manager operator used to update the version of Cassandra. Open the image in a new tab to see the enlarged version.

  

The updating process consists of the following steps:

1. At first, a user creates a Cassandra Custom Resource (CR).

2. KubeDB Provisioner operator watches the Cassandra CR.

3. When the operator finds a Cassandra CR, it creates required number of PetSets and related necessary stuff like secrets, services, etc.

4. Then, in order to update the version of the Cassandra database the user creates a CassandraOpsRequest CR with the desired version.

5. KubeDB Ops-manager operator watches the CassandraOpsRequest CR.

6. When it finds a CassandraOpsRequest CR, it halts the Cassandra object which is referred from the CassandraOpsRequest. So, the KubeDB Provisioner operator doesn’t perform any operations on the Cassandra object during the updating process.

7. By looking at the target version from CassandraOpsRequest CR, KubeDB Ops-manager operator updates the images of all the PetSets.

8. After successfully updating the PetSets and their Pods images, the KubeDB Ops-manager operator updates the image of the Cassandra object to reflect the updated state of the database.

9. After successfully updating of Cassandra object, the KubeDB Ops-manager operator resumes the Cassandra object so that the KubeDB Provisioner operator can resume its usual operations.

In the next doc, we are going to show a step by step guide on updating of a Cassandra database using updateVersion operation.