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+.

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

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

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

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

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.

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

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

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

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

This release provides the following updates:

• PostgreSQL minor version updates
• pgBackrest version updated from 2.10 to 2.13

• 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

This release is a bug fix release, the following is included:

crunchy-vacuum has been deprecated
#993 - Docker pgadmin4 example fails: Could not create pgAdmin4 database
#927 - provide configurable url for root for pgadmin
#973 - run.sh does not error if storage not created
#771 - add backoff limits to example jobs
pgBackrest updated to 2.10
Updated prometheus and grafana versions
Add environment variable to not deploy default grafana dashboards
Documentation updates

This release includes:

• Crunchy Watch has been deprecated, please see the Crunchy Operator for fail over support.
• Updated to the least privaleges that Scheduler needs to run with.
• Fixed harded coded Postgres port in the postgres template.
• Updated pgbackrest to use environment variables.
• Updated multpile examples take not of pgbackrest in particular.
• Added labels to to be used or cleaning up examples.
• #925 Limit listener of temporary pg to unix domain socket - thanks to @gkranis for this fix.
• added sshd back into postgres containers to support pgbackrest integration in the Operator
• added a way to disable node exporter metrics from being collected

Support for PostgreSQL 11.1.
Crunchy DBA container has been deprecated and was replaced with the Crunchy Scheduler Container
#891 Added filesystem metrics missing for PostgreSQL volumes
#847 remove sshd from pg containers
#885 Updated documentation for OCP RBAC setup for running the examples
#855 log_statement configurable for PG containers
#770 Error code displayed when a pg_basebackup that fails.
#745 Fix bashrc and bash_profile
#718 Removed the need of nss_wrapper in the containers
#701 Badger Custom Opts
#688 Update examples to use separate subdirectories
Add permissions to service account - thanks to gadelkareem for submitting the fix
Updated documentation to use Openshift Container Platform 3.11
Added updates and test to the automated test harness.
Added ability to use GIS container with backrest examples.
Other documentation updates and corrections.

Release 2.1.0 provides updates to the latest versions of PostgreSQL. In addition pgmonitor and documentation has been updated.

The following changes, additions, and updates are included:

• PostgreSQL packages updated to 10.5, 9.6.10, 9.5.14
• PGPool packages updated to 3.5.16 (9.5 container) and 3.7.5 (9.6/10 container)
• Data Checksums have been enabled on the images.
• pgmonitor integration has been upgraded
• pg_upgrade example was updated
• Minor formatting changes have been applied to files.
• Minor updates to have been applied to examples
• Documentation has been updated

This release is a major release and includes the following:

• improved testing
• #589 - removed the deprecation warning for users using the older environment variable names in the Postgres container
• #627 - added pre and post hooks into the Postgres container to allow users a means to provide custom script execution as part of the PG container lifecycle
• #548 - fix to pgdump container
• #643 - included a test suite for the Kube and OCP examples
• revised documentation based on Hugo
• #644 - fixed missing volume spec in pgrestore example
• #611 - updated OCP template examples to use storage classes
• #594 - fixed PITR example
• #412 - updated the pgbouncer container and examples to use latest features and be more streamlined
• #661 - added pre and post hooks into the Postgres containers allowing users access to the database lifecycle
• #662, #631 - update pgadmin4 images to latest which fixes a bug in resetting passwords
• updated pgbadger to support incremental report logic
• updated pgbackrest version
• #628 - refactor pgbouncer container adding more features
• better support for GKE/GCP added into to examples and documentation

Release 1.8.3 had the primary goals of improving consistency, readability, and ease of use across the Container Suite; this applies from both a developer and end-user point of view.

The following changes, additions, and updates are included:

• Added an API healthcheck event loop before registering the Grafana dashboard and data source. (Bug Fix)
• Renamed the crunchy-dump container to crunchy-pgdump.
• Renamed the crunchy-restore container to crunchy-pgrestore.
• Refactored OpenShift templates; added new examples, brought templates up-to-date, and consolidated all templates into a single directory.
• DockerHub documentation for all containers has been updated with detailed descriptions. These can be viewed here: https://hub.docker.com/u/crunchydata/
• Kubernetes and OpenShift examples have been merged into a single directory ($CCPROOT/examples/kube). The examples can be run on either environment seamlessly with the use of the $CCP_CLI environment variable.
• Brought all Docker examples in line with the updated Kubernetes and OpenShift examples.
• All examples now create components that imitate the folder name and their function. For instance, if you have a folder named “example”, it will create a pod and service named “example”, a PVC hosting /pgdata called “example-pgdata”, and so on.
• Increased the use of flexible environment variables already in-use across all example scripts, to improve the ability to change a variable once rather than updating multiple hard-coded variables.
• All cleanup scripts for all examples now correctly clean up all created components.
• Altered line in the pg_hba.conf file that is built by default with the crunchy-postgres container for security purposes; changed it from host all all 127.0.0.1/32 trust to host all all 127.0.0.1/32 md5.
• All examples now create PV and PVC’s depending on the environment you are running (NFS, Dynamic, or HostPath). Additional environment variables will be required to be defined in the .bashrc file, detailed here: https://github.com/crunchydata/crunchy-containers/blob/master/docs/install.adoc#configure-container-storage
• All created PV’s now make use of the CCP_STORAGE_CAPACITY and CCP_STORAGE_MODE variables to define the storage size and mode required to be used. This is replacing the current hard-coded variables in place and will require these variables to be set in the .bashrc file.
• As a result of the storage refactoring, the statefulset-dyn example is no longer necessary and has been deprecated.
• All Red Hat Atomic documents are now consolidated into a subdirectory under the main docs/ folder for better organization.
• All logs for the containers have been updated for improved accuracy, consistency, and readability, including new color-coded log information.
• The method by which the $PGROOT environment variable is set has been refactored and is consistently created across different containers.
• Pull request and issue templates have been created to make the process of submitting a PR or issue more consistent and informational.
• An editor configuration file has been added to ensure consistency across different coding platforms.
• Hardcoded backup paths for the pgrestore and restore examples have now been replaced by dynamically grabbing the last backup path from the running backup job.
• #551 - refactored pgrestore and pgdump to take basic defaults
• fixes PITR example and logic

this release includes the following features:

• updated examples to use unique PVCs instead of sharing a common PVC
• updated prometheus and grafana containers to latest versions
• fixed statefulset logic in postgres container, new PG_REPLICA_HOST environment variable added to support statefulset logic, updated statefulset examples
• update the PITR examples
• #368 - updated the exporters within crunchy-collect
• #366 - updated the metrics containers images, removed the need for crunchy-promgateway, updated docs
• updated the pgpool container to work better with Secrets that hold the pgpool configuration, updated the pgpool examples to be more production realistic using a Secret to hold the pgpool config files and also use a Deployment for running the container
• #476 - modified pgadmin4 container for improved security
• modified the examples to use CCP_STORAGE_PATH instead of PV_PATH, also changed to CCP_NFS_IP instead of the previous LOCAL_IP environment variable setting, this impacts previous examples that use the older names.

This is a minor release that includes the following changes from 1.8.0:

• updated PostgreSQL packages (10.3, 9.6.8, 9.5.12)
• new pgaudit examples

This release includes the following changes:

• a new crunchy-restore container that performs a restore from a pgdump or pgdumpall
• fixed issues in 1.7.1 related to OCP permissions that broke the pgbackrest restore capability and sshd capability
• removed openssh-client from all containers
• updated to the latest Postgres releases
• postgres-gis is broken using PG 9.5 due to the PGDG packages not working with PostGIS. This impacts the centos container image.
• added TLS 1.2 requirement to pgadmin4 when running in https mode