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.
  • The controller-runtime libraries 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 spec.monitoring.pgmonitor.exporter.customTLSSecret field.
  • Configure pgBackRest for IPv6 environments using the postgres-operator.crunchydata.com/pgbackrest-ip-version annotation.
  • 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 stdout and stderr when running a SQL file referenced via spec.databaseInitSQL during database initialization. Contributed by Jeff Martin (@jmartin127).
  • The pgnodemx and pg_stat_statements extensions are now automatically upgraded.
  • The postgres-startup init container now logs an error message if the version of PostgreSQL installed in the image does not match the PostgreSQL version specified using spec.postgresVersion.
  • 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)
  • ThedataSource.volumes migration strategy had been improved to better handle PGDATA directories with invalid permissions and a missing postgresql.conf file.


  • A psycopg2 error is no longer displayed when connecting to a database using pgAdmin 4.
  • With the exception of the --repo option itself, PGO no longer prevents users from specifying pgBackRest options containing the string “repo” (e.g. --repo1-retention-full).
  • 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.