# CloudNativePG v1.30.2

2026-11-17 · [Original release notes](https://github.com/cloudnative-pg/cloudnative-pg/releases/tag/v1.30.2) · [Full summary](https://ratatosk.io/en/releases/cloudnativepg/v1.30.2)

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

## Check before upgrading

### Known issues

- **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 -->

## Security (2)

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

- Affects: setups with traffic reaching affected `golang.org/x/net` HTTP/2 client or server paths
- [GO-2026-6603](https://osv.dev/vulnerability/GO-2026-6603), [GO-2026-6610](https://osv.dev/vulnerability/GO-2026-6610), [GO-2026-6611](https://osv.dev/vulnerability/GO-2026-6611), [GO-2026-6612](https://osv.dev/vulnerability/GO-2026-6612), [GO-2026-6617](https://osv.dev/vulnerability/GO-2026-6617), [GO-2026-6860](https://osv.dev/vulnerability/GO-2026-6860), [GO-2026-6866](https://osv.dev/vulnerability/GO-2026-6866)

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.

>   - 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 -->

### PostgreSQL 18.7 is the new default operand image

- Affects: new clusters without a set image, and existing clusters using `imageName` or an `ImageCatalog`
- Additional action: For 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.

>   - **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 -->

## Breaking changes (1)

### Default PgBouncer image updated to 1.26.1

- Affects: Poolers 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.

>   - 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 -->

## Deprecations (1)

### Removal warning for `barmanObjectStore` backups

- Affects: `Backup` and `ScheduledBackup` resources using the `barmanObjectStore` method
- Removed in: 1.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.

>   - `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 -->

## Important fixes (6)

### Instance manager omits missing extension-image paths

- Affects: clusters 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))

### WAL count and size metrics file counting fixed

- Affects: setups 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 -->

### Restored Cluster primary Lease handling fixed

- Affects: Clusters 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))

### Failed backups skipped in `barman-cloud` catalog reads

- Affects: setups 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 -->

### Replica crash loop after hot standby parameter removal fixed

- Affects: replicas 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 -->

### Instance manager wait on frozen postmasters fixed

- Affects: PostgreSQL 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 -->

## Other changes (15)

- Standby archive restores trigger streaming retries
- SSE-C key field for S3-compatible object stores
- Transient connectivity errors logged by `barman-cloud-wal-restore`
- Defaulting operator log lines at debug level
- `kubectl cnpg status` handles missing `pods/exec` permission
- Sidecar plugin Pods recreated on running clusters
- Online snapshot replica WAL archive recovery fixed
- Bootstrapping replicas excluded from standby-slot lists
- CloudNativePG operator stops repeated `status.phaseReason` updates
- Operator stops retrying instance status errors as network failures
- WAL restore end-of-archive marker scope fixed
- One-second retry for plugin requeues without a delay
- Status probe reads system ID from `pg_control` while PostgreSQL is stopped
- Stale Backup reconciliations guarded against duplicate starts and status rollback
- Volume snapshot backup options preserve cluster configuration

---

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