4.5.4-rc.1

Crunchy Data announces the release of PGO, the Postgres Operator 4.5.4.

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

PostgreSQL Operator 4.5.4 release includes the following software versions upgrades:

• PostgreSQL is updated to 13.4, 12.8, 11.13, 10.18, and 9.6.23.
• pgaudit_analyze is now at 1.0.8.
• set_user is now at version 2.0.1.

Changes

• Ensure vendor label is propagated to all PGO managed objects. Reported by @mdraijer.

Fixes

• Allow backup configuration to be changed when a cluster is recreated. For example, allow backup configuration to change from posix to s3 within a new cluster.
• Ensure a SQL policy that contains writes can be applied to a Postgres cluster after a failover.

4.6.4-rc.1

Crunchy Data announces the release of PGO, the Postgres Operator 4.6.4.

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

PostgreSQL Operator 4.6.4 release includes the following software versions upgrades:

• PostgreSQL is updated to 13.4, 12.8, 11.13, 10.18, and 9.6.23.
• PL/Tcl is now included in the PostGIS (crunchy-postgres-gis-ha) container.

Changes

• On using the built-in upgrade tool, the pg-pod-anti-affinity is now removed from the userlabels section of a pgclusters.crunchydata.com custom resource.
• Ensure vendor label is propagated to all PGO managed objects. Reported by (@mdraijer).

Fixes

• Allow backup configuration to be changed when a cluster is recreated. For example, allow backup configuration to change from posix to s3 within a new cluster.
• Ensure a SQL policy that contains writes can be applied to a Postgres cluster after a failover.

4.6.4

Crunchy Data announces the release of PGO, the Postgres Operator 4.6.4.

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

PostgreSQL Operator 4.6.4 release includes the following software versions upgrades:

• PostgreSQL is updated to 13.4, 12.8, 11.13, 10.18, and 9.6.23.
• PL/Tcl is now included in the PostGIS (crunchy-postgres-gis-ha) container.

Changes

• On using the built-in upgrade tool, the pg-pod-anti-affinity is now removed from the userlabels section of a pgclusters.crunchydata.com custom resource.
• Ensure vendor label is propagated to all PGO managed objects. Reported by (@mdraijer).

Fixes

• Allow backup configuration to be changed when a cluster is recreated. For example, allow backup configuration to change from posix to s3 within a new cluster.
• Ensure a SQL policy that contains writes can be applied to a Postgres cluster after a failover.

4.7.2

Crunchy Data announces the release of PGO, the Postgres Operator 4.7.2.

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

PostgreSQL Operator 4.7.2 release includes the following software versions upgrades:

• PostgreSQL is updated to 13.4, 12.8, 11.13, 10.18, and 9.6.23.
• PL/Tcl is now included in the PostGIS (crunchy-postgres-gis-ha) container.

Changes

• The nss_wrapper has been removed from the crunchy-postgres-exporter container.

4.7.2-rc.1

Crunchy Data announces the release of PGO, the Postgres Operator 4.7.2 on August 17, 2021.

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

PostgreSQL Operator 4.7.2 release includes the following software versions upgrades:

• PostgreSQL is updated to 13.4, 12.8, 11.13, 10.18, and 9.6.23.
• PL/Tcl is now included in the PostGIS (crunchy-postgres-gis-ha) container.

Changes

• The nss_wrapper has been removed from the crunchy-postgres-exporter container.

4.7.1

Crunchy Data announces the release of PGO, the Postgres Operator 4.7.1 on July 29, 2021.

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

PostgreSQL Operator 4.7.1 release includes the following software versions upgrades:

• Patroni is now at 2.1.0.

Changes

• On using the built-in upgrade tool, the pg-pod-anti-affinity is now removed from the userlabels section of a pgclusters.crunchydata.com custom resource.
• Ensure vendor label is propagated to all PGO managed objects. Reported by (@mdraijer).
• Improvements to the pv/create-pv-nfs.sh script, which helps with provisioning persistent volumes when using NFS storage. Contributed by Adrian Galbenus (@agalbenus).

Fixes

• Allow backup configuration to be changed when a cluster is recreated. For example, allow backup configuration to change from posix to s3 within a new cluster.
• Ensure a SQL policy that contains writes can be applied to a Postgres cluster after a failover.
• Removed disable_fsgroup: false from the default installation setup. This allows the OpenShift autodetection code to work properly.
• Fix issue in pgBackRest SSHD configuration bootstrap.

4.7.1 Release Candidate 1

v4.7.1-rc.1

Bump version 4.7.1

4.5.3-rc.1

Modify search path for aggregation script

This release still uses dep and requires a different path to
search over.

4.5.3

Crunchy Data announces the release of the PostgreSQL Operator 4.5.3 on June 2, 2021.

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

PostgreSQL Operator 4.5.3 release includes the following software versions upgrades:

• PostgreSQL is at 13.3, 12.7, 11.12, 10.17, and 9.6.22.
• Patroni is now at version 2.0.2.
• pgBouncer for CentOS 8 / UBI 8 is rebuilt to use the libc for its async DNS backend.

Changes

• Revert setting "UsePAM" to "yes" by default as the bug fix in Docker that required that change was applied roughly one year ago.
• Allow for the PGOADMIN_USERNAME, PGOADMIN_PASSWORD, PGOADMIN_ROLENAME credential bootstrap variables to be overriden as part of the OLM and development install process. Contributed by Mathieu Parent (@sathieu).
• Update Helm installer to follow appropriate conventions. Contributed by Jakub Ráček (@kubaracek).

Fixes

• Fix crash due to superfluous trailing whitespace when parsing --backup-opts in pgo backup. Reported by Samir Faci (@safaci2000).
• Fix issue where metrics about pgBackRest backups could not be scraped if the backups were stored in a S3-like environment that requires the use of disabling TLS verification. Reported by (@lphan-clv) and (@dakine1111).
• Fix issue where certain pgAdmin 4 functions did not work (e.g. taking a backup) due to python references in EL8 containers. Reported by (@douggutaby).
• Fix how the pgAdmin 4 Service is identified in pgo test. Prior to this, it was identified as a "primary"; now it is "pgadmin".
• Ensure a Postgres cluster shutdown can execute even if the status subresource of a pgclusters.crunchydata.com custom resource is missing.
• Ensure major upgrades via crunchy-upgrade support PostgreSQL 12 and PostgreSQL 13. Reported by (@lbartnicki92).
• Fix nonbreaking error message that occurs when pgo-scheduler container shuts down in the UBI 8 base container.
• The pgo-deployer and Ansible installer will no longer create an initial TLS secret for the PGO apiserver. PGO apiserver has been able to self-create this for a long time, and PGO defers to that. This fixes an issue that occurred on newer builds where certificates generated by OpenSSL contained incomplete usage blocks, which could cause for these certificates to be properly outright rejected.

4.6.3

Crunchy Data announces the release of the PostgreSQL Operator 4.6.3 on May 25, 2021.

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

PostgreSQL Operator 4.6.3 release includes the following software versions upgrades:

• PostgreSQL is now at 13.3, 12.7, 11.12, 10.17, and 9.6.22.
• pgMonitor is now at 4.4-1.

Changes

• Allow for the PGOADMIN_USERNAME, PGOADMIN_PASSWORD, PGOADMIN_ROLENAME credential bootstrap variables to be overriden as part of the OLM and development install process. Contributed by Mathieu Parent (@sathieu).
• Update Helm installer to follow appropriate conventions. Contributed by Jakub Ráček (@kubaracek)

Fixes

• Fix crash due to superfluous trailing whitespace when parsing --backup-opts in pgo backup. Reported by Samir Faci (@safaci2000).
• Ensure sshd_config is correctly set on an upgrade. This could have manifested with some pgBackRest functionality not working. This can be manually fixed by setting UsePAM no in the sshd_config file in a cluster. Reported by (@douggutaby).
• Fix issue where metrics about pgBackRest backups could not be scraped if the backups were stored in a S3-like environment that requires the use of disabling TLS verification. Reported by (@lphan-clv) and (@dakine1111).
• Fix how the pgAdmin 4 Service is identified in pgo test. Prior to this, it was identified as a "primary"; now it is "pgadmin".
• Fix nonbreaking error message that occurs when pgo-scheduler container shuts down in the UBI 8 base container.
• The pgo-deployer and Ansible installer will no longer create an initial TLS secret for the PGO apiserver. PGO apiserver has been able to self-create this for a long time, and PGO defers to that. This fixes an issue that occurred on newer builds where certificates generated by OpenSSL contained incomplete usage blocks, which could cause for these certificates to be properly outright rejected.