CloudNativePG v1.28.4
Release Notes
Release date: Jun 29, 2026
:::warning This is the final release in the 1.28.x series. Users are strongly encouraged to upgrade to a newer minor version, as 1.28 is no longer supported. :::
Important changes
-
Updated the deprecation notice for native (in-tree) Barman Cloud support to reflect that it will now be removed in CloudNativePG 1.31.0, rather than 1.30.0. Users are still encouraged to migrate to the Barman Cloud Plugin. (#11083)
-
The
clusterreference is now immutable on theDatabase,Pooler,Publication,Subscription, andScheduledBackupresources. Pointing one of these objects at a different cluster has no well-defined semantics and previously left the controllers in an inconsistent state; the update is now rejected at the API server via a CEL validation rule. (#10743)
Enhancements
-
Added a label selector to the
Clusterscale subresource (status.selector), making aClustera validtargetReffor the Vertical Pod Autoscaler (VPA) and Horizontal Pod Autoscaler (HPA), which can now map aClusterto its instance pods. Contributed by @sebv004. (#8996) -
The operator now emits a
WarningPrimaryStatusCheckFailedevent on theClusterwhen the primary pod isReadyfrom the kubelet perspective but the operator's/pg/statuscheck fails and failover is deferred, giving users visibility into the deferral viakubectl describe cluster. (#10509) -
The operator now reloads a CNPG-i plugin automatically when its pods are rolled: it watches the
EndpointSlicesbacking pluginServicesand re-enqueues every cluster using the plugin once the new pods becomeReady, so an upgraded plugin is picked up without waiting for the next resync. (#10836)
Security and Supply Chain
-
CVE-2026-55769/GHSA-x8c2-3p4r-v9r6:search_pathpinning on operator-issued connections: a database owner could plant overloaded built-in operators in thepublicschema and alter thesearch_pathso that operator introspection probes, running as the cluster superuser, resolved those overloads beforepg_catalog, aCWE-426privilege-escalation chain (same class asCVE-2018-1058) that could lead to in-pod RCE viaCOPY ... FROM PROGRAM. The operator now pinssearch_path = pg_catalog, public, pg_tempon every pooled connection so it ships in the startup message and takes precedence over tenant-controlled defaults. (#10774,GHSA-x8c2-3p4r-v9r6) -
CVE-2026-55765/GHSA-w3gf-xc94-wvmj: operator-side SCRAM-SHA-256 password encoding: the operator now SCRAM-SHA-256 encodes cleartext role passwords before issuingCREATE/ALTER ROLE ... PASSWORD, so the literal PostgreSQL parses (and that extensions such aspg_stat_statementsorpgauditmay capture) is the SCRAM verifier rather than the cleartext secret. Pre-hashed (MD5 or SCRAM) values are forwarded unchanged, and the per-Secret annotationcnpg.io/passwordPassthrough: "enabled"opts out. (#10724,GHSA-w3gf-xc94-wvmj)
Changes
-
Added support for Kubernetes 1.35 and enabled unit tests on Kubernetes 1.36. (#10900)
-
Updated the default PostgreSQL version to 18.4. (#10719)
-
Updated the Kubernetes versions used to test the operator on public cloud providers. (#10720, #10563, #11033)
Fixes
-
Fixed
spec.postgresql.parametersaccepting keys that are not valid PostgreSQL parameter names, which could inject arbitrary directives intopostgresql.conf; key names are now validated by the webhook. (#11029) -
Fixed declarative
Database,Publication, andSubscriptionobjects reporting a stale primary-side status forever after their cluster was demoted to a replica; the controller now re-checks the replica condition and watches theClusterso a demotion is detected promptly. (#10871) -
Fixed non-sequential pod names (for example
-1,-3) caused by the instance serial counter being advanced before the correspondingJoband PVCs were created; the bump is now persisted only after those resources exist. (#10491) -
Fixed a switchover deadlock when a WAL-archiver plugin was enabled on an existing cluster: with
primaryUpdateMethod: switchoverthe primary could not be rolled out because a clean demotion needs the archiver sidecar that is still missing. The operator now recreates the primary Pod in place so the sidecar is injected and archiving resumes. The check also covers plugins that inject the archiver as a native sidecar (an init container withrestartPolicy: Always), such as
[truncated]