New to KubeDB? Please start here.

PgBouncer TLS/SSL Encryption

Prerequisite : To configure TLS/SSL in PgBouncer, KubeDB uses cert-manager to issue certificates. So first you have to make sure that the cluster has cert-manager installed. To install cert-manager in your cluster following steps here.

To issue a certificate, the following crd of cert-manager is used:

• Issuer/ClusterIssuer: Issuers, and ClusterIssuers represent certificate authorities (CAs) that are able to generate signed certificates by honoring certificate signing requests. All cert-manager certificates require a referenced issuer that is in a ready condition to attempt to honor the request. You can learn more details here.

• Certificate: cert-manager has the concept of Certificates that define a desired x509 certificate which will be renewed and kept up to date. You can learn more details here.

PgBouncer CRD Specification :

KubeDB uses following crd fields to enable SSL/TLS encryption in PgBouncer.

• spec:
  • sslMode
  • tls:
    • issuerRef
    • certificates
  • connectionPool
    • authType Read about the fields in details from pgbouncer concept,

When, sslMode is set to require, the users must specify the tls.issuerRef field. KubeDB uses the issuer or clusterIssuer referenced in the tls.issuerRef field, and the certificate specs provided in tls.certificate to generate certificate secrets using Issuer/ClusterIssuers specification. These certificates secrets including ca.crt, tls.crt and tls.key etc. are used to configure PgBouncer server, exporter etc. respectively.

How TLS/SSL configures in PgBouncer

The following figure shows how KubeDB enterprise used to configure TLS/SSL in PgBouncer. Open the image in a new tab to see the enlarged version.

Deploying PgBouncer with TLS/SSL configuration process consists of the following steps:

1. At first, a user creates a Issuer/ClusterIssuer cr.

2. Then the user creates a PgBouncer cr which refers to the Issuer/ClusterIssuer cr that the user created in the previous step.

3. KubeDB Provisioner operator watches for the PgBouncer cr.

4. When it finds one, it creates Secret, Service, etc. for the PgBouncer database.

5. KubeDB Ops-manager operator watches for PgBouncer, Issuer/ClusterIssuer, Secret and Service.

6. When it finds all the resources(PgBouncer, Issuer/ClusterIssuer, Secret, Service), it creates Certificates by using tls.issuerRef and tls.certificates field specification from PgBouncer cr.

7. cert-manager watches for certificates.

8. When it finds one, it creates certificate secrets tls-secrets(server, client, exporter secrets etc.) that holds the actual certificate signed by the CA.

9. KubeDB Provisioner operator watches for the Certificate secrets tls-secrets.

10. When it finds all the tls-secret, it creates the related Petset so that PgBouncer database can be configured with TLS/SSL.

In the next doc, we are going to show a step-by-step guide on how to configure a PgBouncer database with TLS/SSL.