Skip to content

4.2.0
Compare
Choose a tag to compare
@jkatz jkatz released this 02 Jan 15:04
· 334 commits to master since this release
v4.2.0
30f75d8

Crunchy Data announces the release of the Crunchy Container Suite 4.2.0 on December 31, 2019.

Crunchy Container Suite 4.2.0 introduces a new container for facilitating high-availability PostgreSQL deployments when deploy by the PostgreSQL Operator](https://github.com/CrunchyData/postgres-operator/). Additionally, version 4.2.0 contains significant enhancements to the image building process that, in some cases, results in 70% improvement when building the images.

The Crunchy Container Suite is released in conjunction with the PostgreSQL Operator.

To build the Crunchy Container Suite 4.2.0, you will need to utilize buildah version 1.9.0 and above.

The Crunchy Container Suite is tested with Docker 1.13+, Kubernetes 1.13+, OpenShift 3.11+, Google Kubernetes Engine (GKE), and VMware Enterprise PKS 1.3+.

Version Updates

  • The PostgreSQL containers now use versions 12.1, 11.6, 10.11, 9.6.16, and 9.5.20.
  • pgBackRest is upgraded to use version 2.20
  • pgBouncer is upgraded to use version 1.12
  • Patroni uses version 1.6.3
  • pgAdmin 4 now correctly reports its version, which is 4.13 or 4.16 depending on which image you use.

Breaking Changes

  • Removed the point-in-time (PITR) functionality from the crunchy-pgbasebackup-restore container as there was not a way to replay the WAL archives properly in the PostgreSQL containers

Features

  • Added the crunchy-postgres-ha and the crunchy-postgres-gis-ha containers, which are used with the PostgreSQL Operator to deliver high-availability PostgreSQL environments
  • Introduction of the crunchyadm sidecar for managing PostgreSQL administrator actions in a Kubernetes environment

Fixes

  • Update the configuration for deploying Prometheus in Kuberentes to set the instance label to be Kubernetes pod label deployment-name and the job label to be the Kubernetes pod label pg-cluster. This makes it easier to filter for the desired data when querying Prometheus
  • Fix PostgreSQL recovery settings from being overwritten in the crunchy-postgres and crunchy-postgres-gis containers running PostgreSQL 12
  • Ensure pgAdmin 4 now correctly reports its version
Assets 2
Loading