Crunchy Postgres for Kubernetes 5.6.x Release notes
Release notes for each of the 5.6.x releases.
Component versions
Crunchy Postgres for Kubernetes | Postgres | pgBackRest | pgbouncer | Patroni | pgadmin |
---|---|---|---|---|---|
5.6.1 | 16.4 | 2.52.1 | 1.22 | 3.1.2 | 4.30, 8.10 |
5.6.0 | 16.3 | 2.51 | 1.22 | 3.1.2 | 4.30, 8.6 |
Postgres extension versions
Crunchy Postgres for Kubernetes version | PostGIS | pgRouting | pgaudit | pg_cron | pg_partman | pgnodemx | set_user | wal2json | TimescaleDB | orafce | pgvector |
---|---|---|---|---|---|---|---|---|---|---|---|
5.6.1 | 2.5.11 (earliest) 3.4.2 (latest) | 2.6.3 (earliest) 3.4.2 (latest) | 1.4.3 (earliest) 16.0 (latest) | 1.6.2 | 5.1.0 | 1.6 | 4.0.1 | 2.5 | 2.15.3 | 4.10.3 | 0.7.3 |
5.6.0 | 2.5.11 (earliest) 3.4.2 (latest) | 2.6.3 (earliest) 3.4.2 (latest) | 1.4.3 (earliest) 16.0 (latest) | 1.6.2 | 5.1.0 | 1.6 | 4.0.1 | 2.5 | 2.14.2 | 4.9.4 | 0.7.0 |
A bold version number indicates that the component version was updated in latest release.
5.6.1
Features
- Use the postgres-operator.crunchydata.com/autoCreateUserSchema=true annotation to automatically create a schema for any Postgres users defined via spec.users. With this setting enabled, CPK creates a writable schema for each user (avoiding the PUBLIC schema, which Postgres 15 secured against unintended writes).
Changes
- PostgreSQL versions 16.4, 15.8, 14.13, 13.16, and 12.20 are now available.
- The pgvector extension is now at version 0.7.3.
- The orafce extension is now at version 4.10.3.
- The TimescaleDB extension is at version 2.15.3 for PG 16, 15, and 14.
- When migrating from Timescale DB 2.14.x, you must run this SQL script after you run
ALTER EXTENSION
. For more details, see the following pull request #6797.
- When migrating from Timescale DB 2.14.x, you must run this SQL script after you run
5.6.0
Features
- Configure your
PostgresCluster
to automatically expand Postgres data volume when additional database storage is needed. - pgAdmin updates
- Enable TLS for pgAdmin deployments using custom TLS certificates.
- Use Postgres as the backend for pgAdmin deployments.
- Have PGO reconcile a pgAdmin Service by defining a service name in your
PGAdmin
spec. - Select a
PostgresCluster
by name in yourPGAdmin
spec. - Manage pgAdmin users via the
PGAdmin
spec
- Set passwords declaratively for users defined under
spec.user
. - Configure the service type for the Postgres replica service.
- Provision Crunchy Bridge clusters using the new
CrunchyBridgeCluster
API.
Changes
SeccompProfile
is now set to RuntimeDefault in all Pods.- The PGAdmin API now utilizes Gunicorn as the web server for any pgAdmin deployments.
- Attempts to use the
PASSWORD
option inspec.users.options
will be rejected.
Fixes
StatefulSets
(pgAdmin and pgBackRest repo hosts) will now recover from a bad rollout.- Various spelling fixes. Contributed by Josh Soref (@jsoref)