4.2.3

Crunchy Data announces the release of the Crunchy Container Suite 4.2.3 on May, 22, 2020.

Crunchy Container Suite 4.2.3 release includes bug fixes reported since the release of version 4.2.3 of the Crunchy Container Suite.

This release includes updates for several packages supported by the PostgreSQL Operator, including:

• The PostgreSQL containers now use versions 12.3, 11.8, 10.13, 9.6.18, and 9.5.22
  • Includes support for LLVM in the PostgreSQL 11+ containers. This allows for the usage of JIT compilation.

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

The Crunchy Container Suite is tested with Docker 1.13+, Kubernetes 1.12+, OpenShift 3.11+, and VMware Enterprise PKS 1.3+.

4.3.0

Crunchy Data announces the release of the Crunchy Container Suite 4.3.0 on May 4, 2020.

Crunchy Container Suite 4.3.0 continues to improve on features that aid high-availability PostgreSQL deployments when deployed by the PostgreSQL Operator.

The Crunchy Container Suite is released in conjunction with the PostgreSQL Operator. For a full list of features, please see the PostgreSQL Operator release notes.

To build the Crunchy Container Suite 4.3.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.2, 11.7, 10.12, 9.6.17, and 9.5.21
  • This now includes support for using the JIT compilation feature introduced in PostgreSQL 11
• PostgreSQL containers now support PL/Python3
• pgBackRest is now at version 2.25
• Patroni is now at version 1.6.5
• postgres_exporter is now at version 0.7.0
• pgAdmin 4 is at 4.18

PostgreSQL Operator is tested with Kubernetes 1.13 - 1.18, OpenShift 3.11+, OpenShift 4.3+, Google Kubernetes Engine (GKE), and VMware Enterprise PKS 1.3+.

Breaking Changes

• The wal_level is now defaulted to logical in the PostgreSQL containers, enabling logical replication
• The crunchy-postgres-ha and derived containers now allow of their target recovery action to be "pause"
• Removed the crunchy-scheduler container, as backup scheduler functionality is provided by the PostgreSQL Operator

Features

• The less package is now available in the crunchy-postgres-ha and derived containers
• The PostgreSQL archive_timeout setting is defaulted to 60 in the crunchy-postgres-ha and derived containers
• Containers now use ed25519 ssh keys

Fixes

• The contents of environmental variables are no longer logged to the container logs
• Ensure a user can create objects in their own PostgreSQL schema
• Setting POSTGRES_EXPORTER_PORT is now optional when specifying DATA_SOURCE_NAME in the crunchy-collect container
• yq is updated to 3.3.0
• Fix a missing variable substitution in the pgAdmin 4 Dockerfile

4.2.2

Crunchy Data announces the release of the Crunchy Container Suite 4.2.2 on February, 18, 2020.

Crunchy Container Suite 4.2.2 release includes bug fixes reported since the release of version 4.2.1 of the Crunchy Container Suite.

This release includes updates for several packages supported by the PostgreSQL Operator, including:

• The PostgreSQL containers now use versions 12.2, 11.7, 10.12, 9.6.17, and 9.5.21
• The PostgreSQL containers now support PL/Python3
• Patroni is updated to version 1.6.4

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

The Crunchy Container Suite is tested with Docker 1.13+, Kubernetes 1.12+, OpenShift 3.11+, and VMware Enterprise PKS 1.3+.

Fixes

• Modification to the container build process
• Consolidation of the Dockerfiles for RHEL7/UBI7 builds

4.2.1

Crunchy Data announces the release of the Crunchy Container Suite 4.2.1 on January 16, 2020.

Crunchy Container Suite 4.2.1 release includes bug fixes reported since the release of version 4.2.0 of the Crunchy Container Suite.

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

The Crunchy Container Suite is tested with Docker 1.13+, Kubernetes 1.12+, OpenShift 3.11+, and VMware Enterprise PKS 1.3+.

Fixes

• Update Dockerfiles to move VOLUME directives after all RUN directives, which would cause issues with running the containers in certain Docker-based environments

4.2.0

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

4.1.1

Crunchy Data announces the release of the Crunchy Container Suite 4.1.1 on November 22, 2019.

Crunchy Container Suite 4.1.1 introduces support for PostgreSQL 12 and PostGIS 2.5, and provides updates other supported versions of PostgreSQL to newer, stable versions. This release also includes bug fixes reported since the release of version 4.1.0 of the Crunchy Container Suite.

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

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

The Crunchy Container Suite is tested with Docker 1.13+, Kubernetes 1.12+, OpenShift 3.11+, and VMware Enterprise PKS 1.3+.

Version Updates

• The PostgreSQL container now uses versions 12.1, 11.6, 10.11, 9.6.16, and 9.5.20.
• The PostGIS container (with PostgreSQL version in parenthesis) has been upgraded to use versions 2.5.3 (12), 2.4.8 (10, 11) and 2.3.10 (9.6).
• pgBackRest is now 2.18

Breaking Changes

• The "sample-app" was removed from the repository, as well as associated Dockerfiles.

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.

2.4.2

Crunchy Data announces the release of the Crunchy Container Suite 2.4.2 on October 15, 2019.

Crunchy Container Suite 2.4.2 updates PostgreSQL and supporting libraries to newer, stable releases and also removes some unused libraries. Additionally, all the containers now build using buildah.

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

The Crunchy Container Suite is tested with Docker 1.13+, Kubernetes 1.12+, OpenShift 3.11+, and VMware Enterprise PKS 1.3+.

Version Updates

• The PostgreSQL container now uses versions 11.5, 10.10, 9.6.15, and 9.5.19. The PostgreSQL container now includes support for PL/Python.
• The PostGIS container (with PostgreSQL version in parenthesis) has been upgraded to use versions 2.4.8 (10, 11) and 2.3.10 (9.6). The PostGIS container now uses PL/R 8.4
• pgBackRest is now 2.17
• pgMonitor now uses version 3.2
• pgAdmin4 now uses version 4.13
• pgBouncer now uses version 1.10
• pgBadger now uses version 11.0
• Grafana uses version 6.3.4
• Prometheus uses version 2.9.2

Breaking Changes

• The node_exporter container is no longer shipped with the PostgreSQL Operator. A detailed explanation of how node-style metrics are handled is available in the "Additional Features" section.
• The Makefile now uses buildah for building the containers instead of Docker. The PostgreSQL Operator can be built with buildah v1.9.0 and above.

Additional Features

• The crunchy-collect container now has separate variables available for connecting to a PostgreSQL database: COLLECT_PG_HOST, COLLECT_PG_PORT, COLLECT_PG_DATABASE, COLLECT_PG_USER, COLLECT_PG_PASSWORD, COLLECT_PG_PARAMS
• Introduce the PG_CTL_START_TIMEOUT, PG_CTL_STOP_TIMEOUT, and PG_CTL_PROMOTE_TIMEOUT variables for the PostgreSQL containers to allow a user to specify how long the pg_ctl [start|stop|promote] commands are allowed to run before timing out. The values default to 60, which is the default in PostgreSQL.
• Allow for the service ports to be specified in the crunchy-pgbadger and crunchy-collect containers
• All license files are now included in the /license directory on container images.

Fixes

• When ENABLED_SSHD is set to true, the PostgreSQL container will start the sshd service before PostgreSQL is started

2.4.1

This is a minor release of the Crunchy Container Suite. It has the following updates:

• PostgreSQL versions were updated.
• Default PostgreSQL to UTF-8

2.3.3

This is a minor release of the Crunchy Container Suite. It has the following updates:

• PostgreSQL versions were updated.
• #1092 Add fix for pgbadger port

Release 2.4.0

• pgBench container and example was added so that you can gather benchmarks easier.
• refactored node exporter out out of the collect image so it is now run as a daemonset.
• environment variable DISABLE_NODE_EXPORTER added to disable node exporter
• cleanup of docker examples
• Added ability to use S3 with pgbackrest via the Crunchy Operator