Crunchy Postgres for Kubernetes 5.7.x Release notes

Release notes for each of the 5.7.x releases.

Component versions

Postgres extension versions

A bold version number indicates that the component version was updated in latest release.

5.7.2

Changes

• Continue when Postgres restore intentionally exits early multiple times
• Always pass a --jobs argument to pg_upgrade
• Patroni is now at version 3.3.5.
• pgBackrest is now at version 2.54.0
• pgAdmin is now at version 8.14.
• orafce is now at version 4.14.0.
• pgvector is now at version 0.8.0.
• The Timescaledb extension is at version 2.17.2 for PG 17, 16, 15, and 14.

5.7.1

Features

• The operator emits a warning event when a postgrescluster is using a major version of Postgres that is no longer receiving updates

Changes

• PostgreSQL versions 17.2, 16.6, 15.10, 14.15, 13.18, and 12.22 are now available.
• Patroni is now at version 3.3.4.

Fixes

• The CrunchyBridgeCluster.spec.secret field is now required.

5.7.0

Features

• Asynchronous archiving by default. CPK will take control of the spool-path. If you have set the spool-path in the backups.pgbackrest.global section of your spec, remove that setting after upgrading. You can also delete that directory. If you would like to opt out of asynchronous archiving, set spec.backups.pgbackrest.global.archive-async: “n”. After upgrading, a new log will be introduced to track WAL archiving at pgdata/pgbackrest/log/db-archive-push-async.log.
• You can now enable backups from replicas within your pgBackRest configuration. Ensure you have at least one Postgres replica available, and then set spec.backups.pgbackrest.global.backup-standby: “y”.
• You can now disable backups when provisioning new Postgres cluster by omitting the backups section from your PostgresCluster spec.
• You can now use Kerberos authentication with pgAdmin4 deployments created via the PGAdmin API.
• Liveness and readiness probes are now enabled by default when the operator is run. Additionally, all CPK installers have been updated to use these probes when creating the operator Deployment.
• You can now make the operator highly available by adding one or more additional replicas to the pgo Deployment.
• You can now configure the operator to watch a certain subset of namespaces using the new PGO_TARGET_NAMESPACES environment variable. This means you can now configure the operator to watch one namespace, all namespaces, or a specific subset of namespaces.
• You can now provide a custom CA cert for Postgres LDAP authentication using the existing spec.config.files method to mount a Secret containing the ca.crt file.
• You can now easily enable or disable CPK feature gates via values.yaml settings when installing CPK via Helm. Contributed by Daniel Holmes (@jaitaiwan)
• You can now leverage Kubernetes Volume Snapshots when cloning a PostgresCluster. Enable VolumeSnapshots feature gate in your operator installation, and then configure a VolumeSnapshotClass within the spec of your source PostgresCluster using spec.backups.snapshots.volumeSnapshotClassName. Now when you clone the PostgresCluster, a snapshot will be leveraged to reduce the overall time to create and initialize the clone.

Changes

• PostgreSQL version 17.0 is now available.
• PostGIS versions 3.4.3 is now available.
• Patroni is now at version 3.3.3.
• pgBackrest is now at version 2.53.1.
• pgBouncer is now at version 1.23.1.
• pgMonitor is now at version 5.1.1.
• pgAdmin is now at version 8.12.
• The pgAudit 17.0 extension is now available.
• The pg_cron extension is now at version 1.6.4.
• The pgvector extension is now at version 0.7.4.
• The pgnodemx extension is now at version 1.7.
• The TimescaleDB extension is at version 2.17.0 for PG 17, 16, 15, and 14.
• pgAdmin and pgBackRest images have tar as required by the kubectl cp command.
• The AutoCreateUserSchema feature gate now defaults to true.

Fixes

• The externalTrafficPolicy is now properly configured for the primary, replica, PgBouncer and pgAdmin Services.