New to KubeDB? Please start here.

updating SingleStore version Overview

This guide will give you an overview on how KubeDB Ops Manager update the version of SingleStore database.

Before You Begin

• You should be familiar with the following KubeDB concepts:
  • SingleStore
  • SingleStoreOpsRequest

How update version Process Works

The following diagram shows how KubeDB Ops Manager used to update the version of SingleStore. 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 SingleStore Custom Resource (CR).

2. KubeDB Provisioner operator watches the SingleStore CR.

3. When the operator finds a SingleStore 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 SingleStore database the user creates a SingleStoreOpsRequest CR with the desired version.

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

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

7. By looking at the target version from SingleStoreOpsRequest CR, KubeDB Ops-manager operator updates the images of all the PetSets. After each image update, the operator performs some checks such as if the oplog is synced and database size is almost same or not.

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

9. After successfully updating of SingleStore object, the KubeDB Ops-manager operator resumes the SingleStore 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 SingleStore database using update operation.