Skip to content

Release 1.19.3
Compare
Choose a tag to compare
@cnp-autobot cnp-autobot released this 13 Jun 10:36
v1.19.3
988bdd3
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.

Release date: June 12, 2023

Enhancements:

  • Add the snapshot command to the cnp plugin to create a consistent cold backup of the cluster from a standby using the Kubernetes VolumeSnapshot standard resource (#1960)
  • First implementation of recovery from a set of CSI VolumeSnapshot resources via the .spec.bootstrap.recovery.volumeSnapshot stanza (#1960)
  • Add pg_failover_slots to managed extensions (#2057)
  • Improved Grafana dashboard with updated instructions in the documentation and the quickstart guide (#1916)
  • Introduce the schemaOnly option in the import stanza, to avoid exporting and importing data when you bootstrap a new Postgres Cluster from one or more existing databases (#2234)
  • Add support for TopologySpreadConstraints to manage scheduling of instance pods (#2202)
  • Add PodMonitor support to the Poolerfor PgBouncer (#2034)
  • Add option to override the default Kubernetes scheduler (#2013)
  • Allow configuration of deployment strategy of a Pooler resource (#1983)
  • Update default PostgreSQL version to 15.3 (#2022)
  • Use PgBouncer 1.19 by default (#2018)

Technical enhancements:

  • Updated k8s kind tested versions (#2054)
  • Use separate transactions to reconcile role credentials. Before this patch, the operator would revert the synchronization of all roles if one failed (#2004)
  • Ensure fencing is removed during cluster restore (#1987)
  • Improve logging when deleting Pods (#2136)

Fixes:

  • Fix unbound variable with k3s engine which could prevent setup on K3’s (#2157)
  • Report the correct PG version in the metrics (#2126)
  • Use the correct walStorage key in the documentation (#2140)
  • Halt reconciliation when the operator cannot connect with the instances, and provide a clear diagnostic on such occasions. This will help clarify cases where network issues obstruct normal operation of EDB Postgres for Kubernetes (#2145), (#2233), and (#2242)
Assets 2
Loading