Supported versions v2.0.0

This page lists the status for currently supported releases of EDB Postgres® AI for CloudNativePG™ Global Cluster.

Naming Scheme

The EDB CloudNativePG Global Cluster (PGD4K) release follows Semantic Versioning 2.0.0 and is structured as follows:

<major>.<minor>.<patch>
  • <major> maps to the supported PGD version. Version 1.x.y supports PGD version 5.x, version 2.x.y supports PGD version 6.x.
  • <minor> is incremented for each supported PG4K Long-Term Support release dependency change.
  • <patch> indexes the patches for the current <minor> release, representing small changes relative to the <minor> release.

Git tags for versions are prefixed with v.

General Support status

EDB CloudNativePG Global Cluster version 1.x is used to manage Postgres Distributed version 5.x. The general support status is as follows:

Note

The following table summarizes the general support status for EDB CloudNativePG Global Cluster. For detailed support status, including supported Kubernetes versions, PG4K versions, Postgres versions, and Postgres Distributed versions, please refer to the Detailed support status section below.

VersionCurrently SupportedRelease Date (first release)Supported Kubernetes VersionsSupported PG4K VersionsSupported Postgres versionsSupported Postgres Distributed versions
2.xYesMar 26, 2026v1.33 -v1.28v14 - v18v6.0.0 -

The Postgres (operand) versions are limited to those supported by EDB Postgres Distributed (PGD).

Important

Please be aware that this page is informative only. The "Platform Compatibility" page from the EDB website contains the official list of supported software and Kubernetes distributions.

Detailed support status

The EDB CloudNativePG Global Cluster (PGD4K) operator uses the PG4K (PG4K) operator to manage each PGD node as a PG4K Cluster. Each minor release reaches its End of Life in alignment with the corresponding PG4K LTS release. For details on the support scope of each PG4K LTS release, please refer to the platform compatibility

VersionCurrently SupportedRelease DateSupported Kubernetes VersionsSupported PG4K VersionsSupported Postgres versionsSupported Postgres Distributed versionsSupported OpenShift VersionsSupported Cert-manager versions
2.0.0YesMar 26, 20261.33, 1.34, 1.35v1.28.1v14 - v18v6.1.0, v6.2.0, v6.3.0v4.16 - v4.21>v1.10.0

PGD Operator manifests

For each EDB CloudNativePG Global Cluster release, we created all-in-one manifests with EDB CloudNativePG Global Cluster and the latest supported PG4K. To deploy those all-in-one manifests on Kubernetes, create the edb-pull-secret in advance and then apply the manifests.

kubectl apply --server-side --force-conflicts -f \
   https://get.enterprisedb.io/pg4k-pgd/pg4k-pgd-2.0.0.yaml
PGD4K releaseNested PG4K releaseManifests
v2.0.0v1.28.1pg4k-pgd-2.0.0.yaml

PGD Operand images

For each minor release of PGD, EDB consistently builds the latest PostgreSQL version integrated with the latest PGD extension. Once a new minor version of PGD is released, EDB switches to build the latest PostgreSQL with the newly released PGD minor.

For example: If PGD 6.2 is the latest minor release, EDB will continue building PGD images with the latest PostgreSQL patches for each supported PostgreSQL version, along with the latest PGD 6.2 release (e.g., PGD 6.2.1). When PGD 6.3 is released, EDB will then update to build images with the latest PostgreSQL patches combined with PGD 6.3.x.

We maintain an imageCatalog for each PGD minor release. Each imageCatalog contains the operand image that includes the latest PostgreSQL patches and the latest PGD patch.

Repository change for PGD operand

We're unifying our repositories, and thus operand image paths will change - please follow the Central Migration Guide to avoid deployment failure and downtime when upgrading.