New to KubeDB? Please start here.

updating ProxySQL version Overview

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

Before You Begin

• You should be familiar with the following KubeDB concepts:
  • ProxySQL
  • ProxySQLOpsRequest

How update Process Works

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

2. KubeDB Community operator watches the ProxySQL CR.

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

5. KubeDB Enterprise operator watches the ProxySQLOpsRequest CR.

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

7. By looking at the target version from ProxySQLOpsRequest CR, KubeDB Enterprise 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 Enterprise operator updates the image of the ProxySQL object to reflect the updated state of the server.

9. After successfully updating of ProxySQL object, the KubeDB Enterprise operator resumes the ProxySQL object so that the KubeDB Community operator can resume its usual operations.

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