New to KubeDB? Please start here.

Overview of ZooKeeper Version Update

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

Before You Begin

• You should be familiar with the following KubeDB concepts:
  • ZooKeeper
  • ZooKeeperOpsRequest

How update version Process Works

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

2. KubeDB Provisioner operator watches the ZooKeeper CR.

3. When the operator finds a ZooKeeper CR, it creates required number of PetSets and other kubernetes native resources like secrets, services, etc.

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

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

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

7. By looking at the target version from ZooKeeperOpsRequest 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 version field of the ZooKeeper object to reflect the updated state of the database.

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