EDB Postgres for Kubernetes 1.18.13 release notes v1
We are in the process of migrating the documentation from the previous EDB Postgres for Kubernetes name to the new EDB CloudNativePG Cluster name. You may see references to both names in this documentation.
Released: 13 Jun 2024
EDB Postgres for Kubernetes version 1.18.13 is an LTS release of EDB Postgres for Kubernetes; there is no corresponding upstream release of CloudNativePG.
Warning
This is expected to be the last release in the 1.18.X series. Users are encouraged to update to a newer minor version soon.
This release of EDB Postgres for Kubernetes includes the following:
Type | Description |
---|---|
Enhancement | Enabled the configuration of the liveness probe timeout via the .spec.livenessProbeTimeout option (#4719) |
Change | Default operand image set to PostgreSQL 16.3 (#4584) |
Change | Removed all RBAC requirements on namespace objects (#4753) |
Bug fix | Prevented fenced instances from entering an unnecessary loop and consuming all available CPU (#4625) |
Bug fix | Resolved an issue where the instance manager on the primary would indefinitely wait for the instance to start after encountering a failure following a stop operation (#4434) |
Bug fix | Fixed a panic in the backup controller that occurred when pod container statuses were missing (#4765) |
Bug fix | Prevented unnecessary shutdown of the instance manager (#4670) |
Bug fix | Prevented unnecessary reloads of PostgreSQL configuration when unchanged (#4531) |
Bug fix | Prevented unnecessary reloads of the ident map by ensuring a consistent and unique method of writing its content (#4648) |
Bug fix | Avoided conflicts during phase registration by patching the status of the resource instead of updating it (#4637) |
Bug fix | Implemented a timeout when restarting PostgreSQL and lifting fencing (#4504) |
Bug fix | Ensured that a replica cluster is restarted after promotion to properly set the archive mode (#4399) |
Bug fix | Ensured correct parsing of the additional rows field returned when the pgaudit.log_rows option was enabled, preventing audit logs from being incorrectly routed to the normal log stream (#4394) |