New to KubeDB? Please start here.

updating Pgpool version Overview

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

Before You Begin

• You should be familiar with the following KubeDB concepts:
  • Pgpool
  • PgpoolOpsRequest

How update version Process Works

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

2. KubeDB Provisioner operator watches the Pgpool CR.

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

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

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

7. By looking at the target version from PgpoolOpsRequest CR, KubeDB Ops-manager operator updates the image of the PetSet.

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

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