Crunchy Postgres for Kubernetes 6.0.x Release notes

Release notes for each of the 6.0.x releases.

6.0.0

Features

Version 1 of the PostgresCluster Custom Resource Definition (CRD) and API is now available. This new version of the PostgresCluster includes the following changes:

  • Mount additional PVC’s and image volumes to any container in your Postgres cluster, including sidecars and jobs.
  • Configure Postgres, pgBackrest, and/or PgBouncer to use custom (i.e., user-provisioned) PVC’s for logging.
  • Define separate/individual log paths for the various pgBackRest components components comprising your PostgresCluster (e.g., the pgBackRest repository host, and any pgBackRest backup or restore Job)
  • Enable auto-grow for Postgres WAL volume and any pgBackRest repository host volumes.
  • Configure the maximum size a volume can grow, as well as the percentage of utilized space that should trigger volume expansion, when using autogrow with a Postgres and/or a pgBackRest volume.
  • The Postgres environment is validated before starting a Postgres major version upgrade, and is left untouched if issues are found.

For guidance on how to upgrade from a v1beta1 PostgresCluster to v1, please see the upgrade guide.

Additionally, please note that you can now build your own containers for use with the Postgres Operator using packages from the PostgreSQL Global Development Group (PGDG). See the build guidance in the documentation for more details.

Breaking Changes

  • The maximum number of PgBouncer configuration settings allowed in a v1beta1 or a v1 PostgresCluster spec is 50.
  • That maximum number of Postgres InstanceSets allowed in a v1 PostgresCluster spec is 16.
  • It is no longer possible to provision pgAdmin 4.30 deployments using the v1 PostgresCluster CRD. Use the PgAdmin API instead.
  • The Postgres log directory is now outside the data directory by default, and directories that contain Postgres data are disallowed.

Changes

  • pgBouncer is now 1.25.1.
  • The AutoGrowVolumes feature gate is now enabled by default.
  • The Kustomize installer for the Postgres Operator has moved from the examples repository to the Postgres Operator repository, and Helm installer is now available via OCI only

Fixes

  • The PgBouncer log file can now be customized using the logfile setting when OpenTelemetry logging is enabled.
  • Major Postgres version upgrades can now proceed even when data checksums have not been enabled for the database cluster.
  • Data directory permissions are now set during bootstrap, and the operator ensures the data directories have group-read permissions.
  • Cluster changes now properly rollout when AutoGrow is enabled and no PVC-based pgBackRest repository exists.