Playing with Elephants ~PostgreSQL and Pgpool-II~

In my previous post I described how to deploy Crunchy Postgres Operator v4 on Kubernetes and use it to achieve disaster recovery and high availability. The new major version, v5 was released last year and the installation methods have significantly changed.  Crunchy Postgres Operator (PGO) v5 allows you to deploy PGO and your PostgreSQL clusters through Kustomize or Helm and manage your PostgreSQL clusters using kubectl command instead of pgo used in v4. This post describes how to install PGO v5 and create PostgreSQL cluster on Amazon EKS using Kustomize. Prerequisites Before you start, make sure you have installed the following tools: AWS CLI eksctl kubectl An access key ID and secret access key An Amazon S3 bucket (In this tutorial we create a bucket named my-postgres-bucket and specify the bucket name in the PostgresCluster YAML file) Creating an Amazon EKS cluster Create a 3 nodes Amazon EKS cluster with the latest Kubernetes version 1.21 in region us-west-2. $ eksctl cr...

In my previous post , I described how to use multi-cluster architecture provided by Crunchy PostgreSQL Operator to achieve disaster recovery and high availability on Kubernetes. As mentioned in the previous post, both  Crunchy PostgreSQL Operator and Zalando PostgreSQL Operator support for multi-cluster deployments. In this post, I am going to describe how to use Zalando PostgreSQL Operator to deploy active/standby PostgreSQL clusters. Multi-Cluster Architecture in Zalando PostgreSQL Operator Below is the multi-cluster architecture in Zalando PostgreSQL Operator. The basic mechanism is same as Crunchy PostgreSQL Operator. But you need to be aware of the following:  At the moment, S3 is only allowed for deploying a standby cluster. This means if you want to setup a standby cluster, you must use S3 for the external storage. On the other hand, Crunchy PostgreSQL Operator allows you to use both S3 and GCS to deploy a standby cluster. As mentioned in the documentation , it is ...