HA AidboxDB

HA AidboxDB installation with Crunchy Operator
High availability for PostgreSQL is complex because it requires multiple components to work seamlessly, can be time-consuming to set up and configure manually, and ongoing maintenance can be challenging. 
Using ready solutions like the Crunchy operator for Kubernetes simplifies the process and improves reliability. Crunchy and similar operators provide a tested and production-ready infrastructure that integrates well with PostgreSQL, as well as features like automatic failover, backups, restores, and upgrades, which can be complex to implement manually. Overall, using a ready solution like Crunchy can reduce complexity and free up time and resources to focus on other aspects of your application.
Crunchy Operator
The Crunchy Operator is an open-source Kubernetes operator that automates the management of PostgreSQL clusters. It provides a simple way to deploy, manage, and operate PostgreSQL clusters in a Kubernetes environment, making it easier to run and scale PostgreSQL workloads.
One of the key benefits of using the Crunchy operator is that it allows for high availability and fault tolerance for your PostgreSQL database. When running a PostgreSQL cluster with the Crunchy operator, you can specify the number of replicas to create, which helps ensure that your database is always available in case of a failure.
Here's how high availability works in terms of the Crunchy operator:
The Crunchy operator deploys a primary PostgreSQL instance and one or more replicas.
The primary instance is responsible for accepting read and write requests and replicating changes to the replicas.
If the primary instance fails, one of the replicas is promoted to become the new primary instance.
The Crunchy operator automatically reconfigures the remaining replicas to replicate from the new primary instance.
This ensures that the cluster remains available even if one or more instances fail.
In addition to high availability, the Crunchy operator also provides other features such as backups and restores, scaling, rolling upgrades, and custom configurations using PostgreSQL custom resource definitions (CRDs).
Install Crunchy
We recommend following official Crunchy Quickstart for how to install and get up and running with PGO. Here are some instructions to get Postgres up and running on Kubernetes:
1.​Fork the Postgres Operator examples repository and clone it to your host machine.
YOUR_GITHUB_UN="<your GitHub username>"
git clone --depth 1 "[email protected]:${YOUR_GITHUB_UN}/postgres-operator-examples.git"
cd postgres-operator-examples
2.Install PGO using kustomize
kubectl apply -k kustomize/install/namespace
kubectl apply --server-side -k kustomize/install/default
3.Verify PGO installation
$ kubectl get pods -n postgres-operator
NAME                           READY   STATUS    RESTARTS   AGE
pgo-7b5d478777-7g6kc           1/1     Running   0          51m
pgo-upgrade-5b576ccfb5-m5qdc   1/1     Running   0          51m
Create cluster
For creating a new PostgreSQL cluster using PGO you should create CRD PostgresCluster. More detailed information about creating a PGO cluster you can found in official documentation.
1.Create aidboxdb.yml file with the following content
aidboxdb.yml
apiVersion: postgres-operator.crunchydata.com/v1beta1
kind: PostgresCluster
metadata:
  name: aidboxdb
  namespace: aidboxdb-db
spec:
  image: healthsamurai/aidboxdb:15.2.0-crunchy
  postgresVersion: 15
  port: 5432
  instances:
    - name: aidboxdb
      replicas: 2
      dataVolumeClaimSpec:
        accessModes:
          - ReadWriteOnce
        resources:
          requests:
            storage: 10Gi
  backups:
    pgbackrest:
      global:
        repo1-retention-full: "30"
        repo1-retention-full-type: time      
      manual:
        options:
          - '--type=full'
        repoName: repo1
      repos:
        - name: repo1
          schedules:
            full: "0 1 * * 0"
            incremental: "0 1 * * 1-6"        
          volume:
            volumeClaimSpec:
              accessModes:
                - ReadWriteOnce
              resources:
                requests:
                  storage: 10Gi
  users:
    - databases:
        - aidbox
      name: aidbox
      options: "SUPERUSER CREATEROLE LOGIN CREATEDB"
  patroni:
    switchover:
      enabled: true
    dynamicConfiguration:
      postgresql:
        pg_hba:
          - host all all 0.0.0.0/0 md5
        parameters:
          listen_addresses : '*'
          shared_preload_libraries : 'pg_stat_statements'
          shared_buffers : '1GB'
​
Look at image property. Generally, you can use the default image provided by Crunchy Operator. But we strongly recommend using healthsamurai/aidboxdb:15.2.0-crunchy  image as the image that is optimized for Aidbox.
Important notes
image: healthsamurai/aidboxdb:15.2.0-crunchy  - we recommend use our aidboxdb image build that is preconfigured for use in PGO
replicas: 2  - in this configuration, we install 1 master and 1 replica
backup options - in this sample, we use local PVC for storing backups. For configuring cloud storages like S3 or GCS you can follow this instructions​
pg_hba: ["host all all 0.0.0.0/0 md5"] - for this tutorial we allow non SSL connection
2.Create a namespace and apply aidboxdb.yml resource
$ kubectl create ns aidboxdb-db
namespace/aidboxdb-db created                                                                                                      ⎈ kind-kind 11:21:57
$ kubectl apply -f aidboxdb.yaml
postgrescluster.postgres-operator.crunchydata.com/aidboxdb created
3.Verify PostgreSQL cluster
$ kubectl get pods -n aidboxdb-db
NAME                         READY   STATUS      RESTARTS   AGE
aidboxdb-aidboxdb-p2tm-0     4/4     Running     0          12m
aidboxdb-aidboxdb-tc58-0     4/4     Running     0          12m
aidboxdb-backup-qvk7-q7qmv   0/1     Completed   0          11m
aidboxdb-repo-host-0         2/2     Running     0          12m
Connect to the cluster 
1.Get connection credentials. Crunchy operator store all connection information in related Secret resource. In our case it aidboxdb-pguser-aidbox. More detailed information you can be found in the connection tutorial.
$ kubectl describe secret aidboxdb-pguser-aidbox -n aidboxdb-db
Name:         aidboxdb-pguser-aidbox
Namespace:    aidboxdb-db
Annotations:  <none>
​
Type:  Opaque
​
Data
====
port:      4 bytes     # Database port 5432
host:      32 bytes    # Local K8S host name
user:      6 bytes     # User name
password:  24 bytes    # Password
dbname:    6 bytes     # database name
verifier:  133 bytes
jdbc-uri:  120 bytes
uri:       101 bytes
2.Now you can set up this parameter for the Aidbox database connection. Look at Install Aidbox in Kubernetes tutorial
Aidbox ConfigMap
apiVersion: v1
kind: ConfigMap
metadata:
  name: aidbox
  namespace: prod
data:
  ...
  PGDATABASE: aidbox
  PGHOST: < host value from aidboxdb-pguser-aidbox secret>
  PGPORT: '5432' 
Aidbox Secret
apiVersion: v1
kind: Secret
metadata:
  name: aidbox
  namespace: prod
data:
  ...
  PGPASSWORD: < password value from aidboxdb-pguser-aidbox secret>
  PGUSER:     < user value from aidboxdb-pguser-aidbox secret>
Backup a cluster
You can specify a schedule backup and retention policy for cluster 
spec:
  backups:
    pgbackrest:
      image: registry.developers.crunchydata.com/crunchydata/crunchy-pgbackrest:ubi8-2.41-4
      global:
        repo1-retention-full: "30"
        repo1-retention-full-type: time      
      manual:
        options:
          - '--type=full'
        repoName: repo1
      repos:
        - name: repo1
          schedules:
            full: "0 1 * * 0"
            incremental: "0 1 * * 1-6"        
          volume:
            volumeClaimSpec:
              accessModes:
                - ReadWriteOnce
              resources:
                requests:
                  storage: 10Gi
Define backup schedule. In this spec we define incremental backup from Monday to Saturday and take one full backup every Sunday at 1 AM
schedules:
  full: "0 1 * * 0"
  incremental: "0 1 * * 1-6"  
Define backup retention policy. In this spec we store all backups 30 days, after that period - delete them
global:
  repo1-retention-full: "30"
  repo1-retention-full-type: time  
Create manual backup
For creating a manual full backup you should annotate postgrescluster resource
$ kubectl annotate -n aidboxdb-db postgrescluster aidboxdb --overwrite \
        postgres-operator.crunchydata.com/pgbackrest-backup="$(date)"
Clone a Postgres Cluster
You can create a single copy of the existing cluster by creating a new one and specify dataSource parameter. In the next example, we  create a stage cluster that is a copy of aidboxdb cluster. Related documentation.
apiVersion: postgres-operator.crunchydata.com/v1beta1
kind: PostgresCluster
metadata:
  name: stage
  namespace: aidboxdb-stage
spec:
  dataSource:
    postgresCluster:
      clusterName: aidboxdb
      clusterNamespace: aidboxdb-db
      repoName: repo1
  image: healthsamurai/aidboxdb:15.2.0-crunchy
  postgresVersion: 15
  instances:
    - dataVolumeClaimSpec:
        accessModes:
        - "ReadWriteOnce"
        resources:
          requests:
            storage: 1Gi
  backups:
    pgbackrest:
      image: registry.developers.crunchydata.com/crunchydata/crunchy-pgbackrest:ubi8-2.41-4
      repos:
      - name: repo1
        volume:
          volumeClaimSpec:
            accessModes:
            - "ReadWriteOnce"
            resources:
              requests:
                storage: 1Gi
Take care of dataSource parameter. In this section we specify the source that will be used for cloning.
  dataSource:
    postgresCluster:
      clusterName: aidboxdb
      clusterNamespace: aidboxdb-db
      repoName: repo1
Restore PITR
When you needed to restore a specific time version of the cluster, or you want to periodically restore you can specify restore option on backup config.
apiVersion: postgres-operator.crunchydata.com/v1beta1
kind: PostgresCluster
metadata:
  name: stage-recovery
  namespace: aidboxdb-stage
spec:
  image: healthsamurai/aidboxdb:15.2.0-crunchy
  postgresVersion: 15
  dataSource:
    postgresCluster:
      clusterName: aidboxdb
      clusterNamespace: aidboxdb-db
      repoName: repo1
  instances:
    - dataVolumeClaimSpec:
        accessModes:
        - "ReadWriteOnce"
        resources:
          requests:
            storage: 1Gi
  backups:
    pgbackrest:
      image: registry.developers.crunchydata.com/crunchydata/crunchy-pgbackrest:ubi8-2.41-4
      restore:
        enabled: true
        repoName: repo1
        options:
        - --type=time
        - --target="2023-04-25 16:20:00-02"
      repos:
      - name: repo1
        volume:
          volumeClaimSpec:
            accessModes:
            - "ReadWriteOnce"
            resources:
              requests:
                storage: 1Gi
Now you need to trigger the recovery process
$ kubectl annotate -n aidboxdb-db  postgrescluster aidboxdb --overwrite \
        postgres-operator.crunchydata.com/pgbackrest-restore="$(date)"
Switchover
To change the primary in your HA cluster, you need to update the PostgresCluster spec to include the following fields:
spec: 
  patroni: 
    switchover: 
      enabled: true
This will prepare your cluster for a switchover. To trigger the switchover, you need to add the postgres-operator.crunchydata.com/trigger-switchover annotation to your custom resource. It's recommended to use a timestamp as the value for the annotation so you can track when you initiated the change.
$ kubectl annotate -n aidboxdb-db  postgrescluster aidboxdb --overwrite \
        postgres-operator.crunchydata.com/trigger-switchover="$(date)"
PGO CLI
PGO Command Line Interface (CLI) for the Crunchy Operator built as a kubectl plugin, the pgo CLI facilitates the creation and management of PostgreSQL clusters created using the Crunchy Postgres Operator. For more information about using the CLI and the various commands available, please see the pgo CLI documentation.
# Create a new backup
$ kubectl pgo backup aidboxdb -n aidboxdb-db
​
# Show backups
$ kubectl pgo show backup aidboxdb -n aidboxdb-db
Monitoring
Configure
Enable monitoring capabilities by configuring monitoring.
spec:
  monitoring:
    pgmonitor:
      exporter:
        image: registry.developers.crunchydata.com/crunchydata/crunchy-postgres-exporter:ubi8-5.3.1-0
Install Prometheus stack
Install all parts manually
​prometheus - metrics and alerting open-source monitoring solution
​grafana - open-source observability tool
Or install Prebuild prometheus stack for Kubernetes
​kube-prometheus - Prebuild prometheus stack for Kubernetes
Scrape config
Configure scrape config for prometheus and PGO Crunchy Operator
- job_name: crunchy-postgres-exporter
  kubernetes_sd_configs:
  - role: pod
  relabel_configs:
  - source_labels:
    - __meta_kubernetes_pod_label_postgres_operator_crunchydata_com_crunchy_postgres_exporter
    - __meta_kubernetes_pod_label_crunchy_postgres_exporter
    action: keep
    regex: true
    separator: ''
  - source_labels:
    - __meta_kubernetes_pod_container_port_number
    action: drop
    regex: 5432
  - source_labels:
    - __meta_kubernetes_pod_container_port_number
    action: drop
    regex: 10000
  - source_labels:
    - __meta_kubernetes_pod_container_port_number
    action: drop
    regex: 8009
  - source_labels:
    - __meta_kubernetes_pod_container_port_number
    action: drop
    regex: 2022
  - source_labels:
    - __meta_kubernetes_pod_container_port_number
    action: drop
    regex: "^$"
  - source_labels:
    - __meta_kubernetes_namespace
    action: replace
    target_label: kubernetes_namespace
  - source_labels:
    - __meta_kubernetes_pod_name
    target_label: pod
  - source_labels:
    - __meta_kubernetes_pod_label_postgres_operator_crunchydata_com_cluster
    - __meta_kubernetes_pod_label_pg_cluster
    target_label: cluster
    separator: ''
    replacement: "$1"
  - source_labels:
    - __meta_kubernetes_namespace
    - cluster
    target_label: pg_cluster
    separator: ":"
    replacement: "$1$2"
  - source_labels:
    - __meta_kubernetes_pod_ip
    target_label: ip
    replacement: "$1"
  - source_labels:
    - __meta_kubernetes_pod_label_postgres_operator_crunchydata_com_instance
    - __meta_kubernetes_pod_label_deployment_name
    target_label: deployment
    replacement: "$1"
    separator: ''
  - source_labels:
    - __meta_kubernetes_pod_label_postgres_operator_crunchydata_com_role
    - __meta_kubernetes_pod_label_role
    target_label: role
    replacement: "$1"
    separator: ''
​
​
Storage - Previous
Aidbox & FHIR formats
Next - Storage
Backup and Restore
Last modified 4mo ago