New to KubeDB? Please start here.

Reconfiguring TLS of Pgpool

This guide will give an overview on how KubeDB Ops-manager operator reconfigures TLS configuration i.e. add TLS, remove TLS, update issuer/cluster issuer or Certificates and rotate the certificates of a Pgpool.

Before You Begin

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

How Reconfiguring Pgpool TLS Configuration Process Works

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

  

The Reconfiguring Pgpool TLS process consists of the following steps:

1. At first, a user creates a Pgpool Custom Resource Object (CRO).

2. KubeDB Provisioner operator watches the Pgpool CRO.

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 the TLS configuration 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 TLS process.

7. Then the KubeDB Ops-manager operator will add, remove, update or rotate TLS configuration based on the Ops Request yaml.

8. Then the KubeDB Ops-manager operator will restart all the Pods of the pgpool so that they restart with the new TLS configuration defined in the PgpoolOpsRequest CR.

9. After the successful reconfiguring of the Pgpool TLS, 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 TLS configuration of a Pgpool using PgpoolOpsRequest CRD.