CloudNativePG v1.30.0-rc1
Release Notes
Release date: Jun 19, 2026
Important changes
- 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)
Features
-
Primary
Leasefor safe primary election: introduced a KubernetesLeaseobject (named after the cluster) that acts as a mutex serializing primary promotion: the instance manager must hold the lease before acting as primary and releases it on clean shutdown so replicas can promote without waiting for the full TTL. Timings are configurable via the new.spec.primaryLeasestanza. The lease is a promotion gate, not a fence — primary isolation remains responsible for fencing. (#10627) -
DatabaseRoleCRD for declarative role management: introduced aDatabaseRolecustom resource that manages a PostgreSQL role as a standalone Kubernetes object, instead of declaring it inline in theCluster's.spec.managed.rolesstanza. Each role gets its own lifecycle, status, and RBAC, which suits GitOps workflows and lets role definitions live next to the applications that own them. The spec reuses the sameRoleConfigurationstructure as the inline method, so migrating a role is a matter of moving the stanza into its own manifest. AdatabaseRoleReclaimPolicyfield (retain, the default, ordelete) controls what happens to the role when the resource is deleted, mirroring persistent volumes. (#6155) -
TLS client certificates for declarative roles: a
DatabaseRolecan now include aclientCertificateblock to have the operator automatically generate and renew a TLS client certificate, signed by the cluster's client CA and stored in a<databaserole-name>-client-certSecret. This enables password-free PostgreSQLcertauthentication; the Secret is cleaned up when the feature is disabled or theDatabaseRoleis deleted. (#10896) -
PgBouncer image management via image catalogs: the
Poolerresource can now reference an entry in anImageCatalogorClusterImageCatalogthrough the newspec.pgbouncer.imageCatalogReffield, centralizing PgBouncer image management. When a catalog entry is updated, all referencingPoolersare automatically reconciled and roll out the new image without any change to their spec. The resolved image is reported instatus.image, and a newstatus.phase(active,paused,inactive, orfailed) — also surfaced as aPhasecolumn inkubectl get pooler— summarizes the lifecycle. (#10568)
Enhancements
-
Enabled
pg_upgradein-place major upgrades to PostgreSQL 19 or later for clusters that use Image Volume extensions, building on the extension-path support added topg_upgradein PostgreSQL 19. During the upgradeJob, the source- and target-version extension images are mounted side by side, so the old server keeps its libraries and a failed upgrade reverts cleanly. (#10366) -
Added TLS support for the
Poolermetrics endpoint via.spec.monitoring.tls.enabled. When enabled, the metrics server is served over HTTPS, reusing the certificate and key from.spec.pgbouncer.clientTLSSecretand reloading it on every handshake to support rotation without a restart; the generatedPodMonitorscrapes overhttpsaccordingly. (#10466) -
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) -
Added the
ENABLE_WEBHOOK_NAMESPACE_SUFFIXflag, which suffixes the operator's webhook configuration names with-<OPERATOR_NAMESPACE>so that multiple operator instances can coexist on the same cluster. The operator only looks up these configurations; users must create and maintain them. Contributed by @maxlengdell. (#10420) -
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) -
Instance serial numbers are now assigned by reusing the lowest free slot among existing instance names, instead of always incrementing a global counter. Pod and PVC names stay stable across instance recreation (for example, an instance recreated after a node drain comes back with the same name), and serials freed by deleted instances are reclaimed. A new
Initializedcluster condition reports whether the cluster has completed its fir
[truncated]