Crunchy Data announces the release of Crunchy Postgres for Kubernetes 5.3.0.
Crunchy Postgres for Kubernetes is powered by PGO, the open source Postgres Operator from Crunchy Data. PGO is released in conjunction with the Crunchy Container Suite.
Crunchy Postgres for Kubernetes 5.3.0 includes the following software versions upgrades:
- PostgreSQL version 15.1 is now available.
- pgMonitor is now at version 4.8.0.
controller-runtimelibraries have been updated to 0.12.3.
- Go 1.19 is now utilized to build Crunchy Postgres for Kubernetes.
Additionally, the pgo CLI version 0.2.0 is now available.
Read more about how you can get started with Crunchy Postgres for Kubernetes. We recommend forking the Postgres Operator examples repo.
Note: TimescaleDB and pgAdmin 4 are not currently supported for use with PostgeSQL 15.
- PostgreSQL 15 support.
- Enable TLS for the PostgreSQL exporter using the new
- Configure pgBackRest for IPv6 environments using the
- Configure the TTL for pgBackRest backup Jobs.
- Use Helm’s OCI registry capability to install Crunchy Postgres for Kubernetes.
- JIT is now explicitly disabled for the monitoring user, allowing users to opt-into using JIT elsewhere in the database without impacting exporter functionality. Contributed by Kirill Petrov (@chobostar).
- PGO now logs both
stderrwhen running a SQL file referenced via
spec.databaseInitSQLduring database initialization. Contributed by Jeff Martin (@jmartin127).
pg_stat_statementsextensions are now automatically upgraded.
postgres-startupinit container now logs an error message if the version of PostgreSQL installed in the image does not match the PostgreSQL version specified using
- Limit the monitoring user to local connections using SCRAM authentication. Contributed by Scott Zelenka (@szelenka)
- Skip a scheduled backup when the prior one is still running. Contributed by Scott Zelenka (@szelenka)
dataSource.volumesmigration strategy had been improved to better handle
PGDATAdirectories with invalid permissions and a missing
psycopg2error is no longer displayed when connecting to a database using pgAdmin 4.
- With the exception of the
--repooption itself, PGO no longer prevents users from specifying pgBackRest options containing the string “repo” (e.g.
- PGO now properly filters Jobs by namespace when reconciling restore or data migrations Job, ensuring PostgresClusters with the same name can be created within different namespaces.
- The Major PostgreSQL Upgrades API (
PGUpgrade) now properly handles clusters that have various extensions enabled.