New to KubeDB? Please start here.

Reconfiguring Pgpool

This guide will give an overview on how KubeDB Ops-manager operator reconfigures Pgpool.

Before You Begin

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

How Reconfiguring Pgpool Process Works

The following diagram shows how KubeDB Ops-manager operator reconfigures Pgpool. Open the image in a new tab to see the enlarged version.

  

The Reconfiguring Pgpool 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 PetSet and related necessary stuff like secrets, services, etc.

4. Then, in order to reconfigure of the Pgpool, the user creates a PgpoolOpsRequest CR with desired information.

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

6. When it finds a PgpoolOpsRequest CR, it pauses 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 reconfiguring process.

7. Then the KubeDB Ops-manager operator will replace the existing configuration with the new configuration provided or merge the new configuration with the existing configuration according to the PgpoolOpsRequest CR.

8. Then the KubeDB Ops-manager operator will restart the related PetSet Pods so that they restart with the new configuration defined in the PgpoolOpsRequest CR.

9. After the successful reconfiguring of the Pgpool, the KubeDB Ops-manager operator resumes the Pgpool object so that the KubeDB Provisioner operator resumes its usual operations.

In the next docs, we are going to show a step-by-step guide on reconfiguring Pgpool database components using PgpoolOpsRequest CRD.