RATATOSK
← All releases

CloudNativePGv1.30.2

Security 2Breaking changes 1Deprecations 1Important fixes 6Other changes 15

Get CloudNativePG alerts

Email is sent weekly only when there are changes to check; critical security advisories are sent immediately.

Check before upgrading

Known issues1
PostgreSQL 14 community fixes ended

The PostgreSQL community stopped fixing PostgreSQL 14 on November 12, 2026. PostgreSQL 15 is to stop receiving fixes on November 11, 2027.

  - **PostgreSQL 14 is no longer supported**: the PostgreSQL community stopped fixing PostgreSQL 14 on November 12, 2026, and CloudNativePG supports a major version only as long as PostgreSQL does. If you still run PostgreSQL 14, plan an upgrade to a newer major version. PostgreSQL 15 stops receiving fixes on November 11, 2027. ([\#11935](https://github.com/cloudnative-pg/cloudnative-pg/pull/11935)) <!-- 1.28 -->
github.com/cloudnative-pg/cloudnative-pg/releases/tag/v1.30.2

Security2

golang.org/x/net HTTP/2 and HTML handling flaws fixed

Affectssetups with traffic reaching affected golang.org/x/net HTTP/2 client or server paths

Before the upgrade, affected HTTP/2 paths could crash, refund flow control twice, consume excessive CPU, mishandle malformed framing-related headers, or allocate disproportionate memory when peers reset streams, send repeated settings frames, or declare many trailer fields. The update also fixes quadratic allocations from certain HTML text inputs and namespace changes after rendering and reparsing; x/net/html is an indirect dependency not imported by CloudNativePG’s code.

Show release-note lines
  - Updated `golang.org/x/net` to v0.62.0, fixing GO-2026-6617, GO-2026-6612, GO-2026-6611, GO-2026-6610, GO-2026-6603, GO-2026-6860 and GO-2026-6866, and bumped the other `golang.org/x` modules. ([\#11631](https://github.com/cloudnative-pg/cloudnative-pg/pull/11631), <!-- 1.28 --> [\#11867](https://github.com/cloudnative-pg/cloudnative-pg/pull/11867)) <!-- 1.28 -->
github.com/cloudnative-pg/cloudnative-pg/releases/tag/v1.30.2

PostgreSQL 18.7 is the new default operand image

Affectsnew clusters without a set image, and existing clusters using imageName or an ImageCatalog
Additional actionFor existing clusters, imageName or the ImageCatalog must be changed to 18.7, 17.12, 16.16, or 15.20 to get the fixes.

The updated images fix several CVEs, but existing clusters do not receive the image change automatically.

Show release-note lines
  - **PostgreSQL 18.7 is the new default image**: the default operand image is now `18.7-system-trixie`, which fixes several CVEs. It applies only to new clusters that don't set an image. To get the fixes, update existing clusters to 18.7, 17.12, 16.16 or 15.20 by changing `imageName` or the `ImageCatalog`. Before updating, read the [PostgreSQL 18.7 announcement](https://www.postgresql.org/about/news/postgresql-187-1712-1616-1520-1425-and-19-rc-2-released-3442/) and the release notes it links. ([\#11833](https://github.com/cloudnative-pg/cloudnative-pg/pull/11833)) <!-- 1.28 -->
github.com/cloudnative-pg/cloudnative-pg/releases/tag/v1.30.2

Breaking changes1

Default PgBouncer image updated to 1.26.1

AffectsPoolers that use the default PgBouncer image

The default image was previously 1.25.2. These poolers roll out the new image when the operator is upgraded.

Show release-note lines
  - Updated the default PgBouncer image from 1.25.2 to 1.26.1. Poolers that use the default image roll out the new version when the operator is upgraded. ([\#11571](https://github.com/cloudnative-pg/cloudnative-pg/pull/11571), <!-- 1.28 --> [\#11704](https://github.com/cloudnative-pg/cloudnative-pg/pull/11704)) <!-- 1.28 -->
github.com/cloudnative-pg/cloudnative-pg/releases/tag/v1.30.2

Deprecations1

Removal warning for barmanObjectStore backups

AffectsBackup and ScheduledBackup resources using the barmanObjectStore method
Removed in1.32

The warning concerns removal of native Barman Cloud support in 1.32; Cluster resources already had it. This warning behavior was already present in the preceding release, so upgrading adds no new warning.

Show release-note lines
  - `Backup` and `ScheduledBackup` resources that use the `barmanObjectStore` method now return an admission warning about the removal of native Barman Cloud support in 1.32, as `Cluster` resources already did. ([\#11725](https://github.com/cloudnative-pg/cloudnative-pg/pull/11725)) <!-- 1.28 -->
github.com/cloudnative-pg/cloudnative-pg/releases/tag/v1.30.2

Important fixes6

  • Instance manager omits missing extension-image paths
    Affectsclusters using extension images with configured default or custom paths

    When an extension image lacked a directory named by a default or custom path, such as share in an image containing only lib, the generated extension_control_path and dynamic_library_path listed it anyway, though PostgreSQL silently ignored it. They now omit missing directories, including custom paths, without raising an error.

      - `extension_control_path` and `dynamic_library_path` no longer list directories that are missing from an extension image, for example `share` in an image that ships only `lib`. ([\#11652](https://github.com/cloudnative-pg/cloudnative-pg/pull/11652))
    github.com/cloudnative-pg/cloudnative-pg/releases/tag/v1.30.2
  • WAL count and size metrics file counting fixed
    Affectssetups using the WAL count and size metrics(Inferred)

    The metrics counted .partial, .backup and .history files.

      - Fixed the WAL count and size metrics counting `.partial`, `.backup` and `.history` files. ([\#9967](https://github.com/cloudnative-pg/cloudnative-pg/pull/9967)) <!-- 1.28 -->
    github.com/cloudnative-pg/cloudnative-pg/releases/tag/v1.30.2
  • Restored Cluster primary Lease handling fixed
    AffectsClusters using OwnerReferencesPermissionEnforcement

    When a Cluster was recreated over leftover resources, the operator could not adopt the existing primary Lease and the Cluster remained in Unable to create required cluster objects. For restores over orphan PVCs with no status, adopting an ownerless stale Lease could delay the new primary by a lease duration; the operator now deletes that Lease and creates a fresh one, while adopting other leftover Leases. Manually managed RBAC must grant delete on leases for these operations to work.

      - The operator now needs the `delete` permission on `leases`. Users who manage the RBAC manually must add it. ([\#11609](https://github.com/cloudnative-pg/cloudnative-pg/pull/11609))
      - Fixed a `Cluster` recreated over leftover resources (for example by a backup tool) staying in `Unable to create required cluster objects` with `cannot set an ownerRef on a resource you can't delete`. This happened with the `OwnerReferencesPermissionEnforcement` admission plugin. When restoring over orphan PVCs, the operator now deletes the stale primary `Lease`, so the new primary does not wait for it to expire. ([\#11609](https://github.com/cloudnative-pg/cloudnative-pg/pull/11609))
    github.com/cloudnative-pg/cloudnative-pg/releases/tag/v1.30.2
  • Failed backups skipped in barman-cloud catalog reads
    Affectssetups using barman-cloud to read a backup catalog(Inferred)
      - Updated the `barman-cloud` library to v0.7.0, which skips failed backups when it reads the backup catalog. ([\#11711](https://github.com/cloudnative-pg/cloudnative-pg/pull/11711)) <!-- 1.28 -->
    github.com/cloudnative-pg/cloudnative-pg/releases/tag/v1.30.2
  • Replica crash loop after hot standby parameter removal fixed
    Affectsreplicas using hot standby parameters such as max_connections

    After a hot standby parameter was removed from .spec.postgresql.parameters, replicas could crash loop with recovery aborted because of insufficient parameter settings. They no longer crash loop with that error in this situation.

      - Fixed replicas crash looping with `recovery aborted because of insufficient parameter settings` after a hot standby parameter such as `max_connections` was removed from `.spec.postgresql.parameters`. Contributed by @ichibahn. ([\#11236](https://github.com/cloudnative-pg/cloudnative-pg/pull/11236)) <!-- 1.28 -->
    github.com/cloudnative-pg/cloudnative-pg/releases/tag/v1.30.2
  • Instance manager wait on frozen postmasters fixed
    AffectsPostgreSQL instances with a postmaster that can freeze

    When a frozen postmaster accepted connections but never answered, the instance manager could wait forever, blocking instance status, the metrics exporter, and the check before an in-tree backup. Local connection attempts now time out after 5 seconds instead.

      - Fixed the instance manager waiting forever on a frozen postmaster, one that accepts connections but never answers. This blocked the instance status, the metrics exporter and the check before an in-tree backup. Local connection attempts to PostgreSQL now time out after 5 seconds. ([\#11718](https://github.com/cloudnative-pg/cloudnative-pg/pull/11718)) <!-- 1.28 -->
    github.com/cloudnative-pg/cloudnative-pg/releases/tag/v1.30.2
Other changes15
  • Standby archive restores trigger streaming retries
      - **Streaming retry for standbys on the WAL archive**: PostgreSQL tries streaming only after a restore from the archive fails. If WAL is produced about as fast as it is restored, that may never happen, and the standby stays on the archive, with no WAL receiver and no part in synchronous replication. Now, after 30 seconds of continuous restores, WAL restore fails on purpose for 5 seconds, so PostgreSQL tries streaming. These failures are expected and can appear in the logs. ([\#11868](https://github.com/cloudnative-pg/cloudnative-pg/pull/11868)) <!-- 1.28 -->
    github.com/cloudnative-pg/cloudnative-pg/releases/tag/v1.30.2
  • SSE-C key field for S3-compatible object stores
      - **Server-side encryption with customer-provided keys (SSE-C)**: added `sseCustomerKey` in `s3Credentials`, to use SSE-C with S3-compatible object stores. It works with backups, WAL archiving and recovery. ([\#11711](https://github.com/cloudnative-pg/cloudnative-pg/pull/11711), <!-- 1.28 --> [\#11775](https://github.com/cloudnative-pg/cloudnative-pg/pull/11775)) <!-- 1.28 -->
    github.com/cloudnative-pg/cloudnative-pg/releases/tag/v1.30.2
  • Transient connectivity errors logged by barman-cloud-wal-restore
      - Transient network errors from `barman-cloud-wal-restore` are now logged (needs Barman 3.20.0 or later). ([\#11541](https://github.com/cloudnative-pg/cloudnative-pg/pull/11541)) <!-- 1.28 -->
    github.com/cloudnative-pg/cloudnative-pg/releases/tag/v1.30.2
  • Defaulting operator log lines at debug level
      - Moved the "Defaulting for ..." operator log lines from info to debug level. They were printed at every reconciliation and hid other messages. ([\#11790](https://github.com/cloudnative-pg/cloudnative-pg/pull/11790)) <!-- 1.28 -->
    github.com/cloudnative-pg/cloudnative-pg/releases/tag/v1.30.2
  • kubectl cnpg status handles missing pods/exec permission
          - `kubectl cnpg status` no longer fails without the `pods/exec` permission. It shows `not permitted: requires the pods/exec permission` instead of the size and configuration sections. ([\#11687](https://github.com/cloudnative-pg/cloudnative-pg/pull/11687)) <!-- 1.28 -->
    github.com/cloudnative-pg/cloudnative-pg/releases/tag/v1.30.2
  • Sidecar plugin Pods recreated on running clusters
      - Fixed enabling a sidecar plugin on a running cluster. Pods created before that have no sidecar until they are recreated. They logged `Unknown plugin` errors, their metrics scrapes failed, and a switchover could wait forever. When the plugin archives WAL, the former primary crash looped until the Pod was deleted. The operator now recreates it. ([\#11858](https://github.com/cloudnative-pg/cloudnative-pg/pull/11858)) <!-- 1.28 -->
    github.com/cloudnative-pg/cloudnative-pg/releases/tag/v1.30.2
  • Online snapshot replica WAL archive recovery fixed
      - Fixed replicas created from an online volume snapshot ignoring the `backup_label` and `tablespace_map` stored in the snapshot. PostgreSQL did crash recovery and did not fetch WAL from the archive. ([\#11847](https://github.com/cloudnative-pg/cloudnative-pg/pull/11847)) <!-- 1.28 -->
    github.com/cloudnative-pg/cloudnative-pg/releases/tag/v1.30.2
  • Bootstrapping replicas excluded from standby-slot lists
      - Fixed logical decoding stalling while a new replica was bootstrapping, with `synchronizeLogicalDecoding` enabled. The replica is now left out of `synchronized_standby_slots` (or `pg_failover_slots.standby_slot_names`) until its volume is initialized. ([\#11802](https://github.com/cloudnative-pg/cloudnative-pg/pull/11802)) <!-- 1.28 -->
    github.com/cloudnative-pg/cloudnative-pg/releases/tag/v1.30.2
  • CloudNativePG operator stops repeated status.phaseReason updates
      - Fixed `status.phaseReason` being cleared and set again several times a second while a cluster was being created or changed, for example "Some instances are not yet active". This loaded the API server and made `kubectl get cluster -w` noisy. ([\#11789](https://github.com/cloudnative-pg/cloudnative-pg/pull/11789))
    github.com/cloudnative-pg/cloudnative-pg/releases/tag/v1.30.2
  • Operator stops retrying instance status errors as network failures
      - Fixed the operator retrying instance status requests that failed with an error response, as if the failure was a network error. During a switchover the old primary answers with an error while PostgreSQL is stopped, so each reconciliation waited about 1.6 seconds, which slowed the whole switchover. Contributed by @kabbydriver. ([\#11793](https://github.com/cloudnative-pg/cloudnative-pg/pull/11793)) <!-- 1.28 -->
    github.com/cloudnative-pg/cloudnative-pg/releases/tag/v1.30.2
  • WAL restore end-of-archive marker scope fixed
      - Fixed WAL restore reporting the end of the WAL archive on the wrong timeline. A replica restored from a snapshot could miss valid WAL of the new timeline and replay WAL of the parent timeline instead. Contributed by @ardentperf. ([\#11133](https://github.com/cloudnative-pg/cloudnative-pg/pull/11133)) <!-- 1.28 -->
    github.com/cloudnative-pg/cloudnative-pg/releases/tag/v1.30.2
  • One-second retry for plugin requeues without a delay
      - Fixed a `Cluster` not being reconciled again when a plugin asked for a retry without a delay. For example, a `Cluster` created before the `ObjectStore` of the Barman Cloud plugin stayed in `BootstrapPending`. The operator now retries after one second. Contributed by @valeriodelsarto. ([\#11683](https://github.com/cloudnative-pg/cloudnative-pg/pull/11683)) <!-- 1.28 -->
    github.com/cloudnative-pg/cloudnative-pg/releases/tag/v1.30.2
  • Status probe reads system ID from pg_control while PostgreSQL is stopped
      - Fixed `ConsistentSystemID` turning `False` while PostgreSQL is not running, for example in replica clusters after a demotion, or on fenced instances. The system ID is now read from disk, so it no longer needs a running PostgreSQL. ([\#11645](https://github.com/cloudnative-pg/cloudnative-pg/pull/11645)) <!-- 1.28 -->
    github.com/cloudnative-pg/cloudnative-pg/releases/tag/v1.30.2
  • Stale Backup reconciliations guarded against duplicate starts and status rollback
      - Fixed a `Backup` that could be started more than once, or moved back to `pending` after it started. ([\#11617](https://github.com/cloudnative-pg/cloudnative-pg/pull/11617)) <!-- 1.28 -->
    github.com/cloudnative-pg/cloudnative-pg/releases/tag/v1.30.2
  • Volume snapshot backup options preserve cluster configuration
      - `cnpg` plugin:
          - Fixed `kubectl cnpg backup` for volume snapshot backups: when only one of `--immediate-checkpoint` and `--wait-for-archive` was set, the other option used its default instead of the value in `.spec.backup.volumeSnapshot.onlineConfiguration`. ([\#11733](https://github.com/cloudnative-pg/cloudnative-pg/pull/11733)) <!-- 1.28 -->
    github.com/cloudnative-pg/cloudnative-pg/releases/tag/v1.30.2

Summaries are produced by AI, so they can be wrong, and they are provided without warranty.