Note
CloudNativePG 1.29+ and the extensions Stanza
The catalogs in this directory are currently the mainstream definitions for older CNPG versions.
- For CNPG 1.29+: Please use the manifests in the
image-catalogs-extensions/directory to leverage the newextensionsstanza and PostgreSQL 18 support forextensions_control_path.
Roadmap Note: In the coming months, once CloudNativePG 1.28 reaches EOL,
the catalogs in this main folder will be updated to support the extensions
format directly, and the temporary image-catalogs-extensions/ directory
will be decommissioned.
This directory contains the official ClusterImageCatalog manifests
maintained by CloudNativePG.
Each catalog defines the latest container images for all supported PostgreSQL
major versions, based on a specific image type (e.g. minimal) and
Debian release (e.g. trixie).
By applying a catalog, administrators ensure that CloudNativePG clusters automatically upgrade to the latest patch release within a given PostgreSQL major version.
Install a single catalog (e.g. minimal images on Debian trixie):
kubectl apply -f \
https://raw.githubusercontent.com/cloudnative-pg/artifacts/refs/heads/main/image-catalogs/catalog-minimal-trixie.yamlInstall all catalogs at once:
kubectl apply -k \
https://github.com/cloudnative-pg/artifacts/image-catalogs?ref=mainCloudNativePG cryptographically signs all official image catalogs. Verifying these signatures ensures that assets originate from official CloudNativePG repositories and were published through our automated release workflow.
Prerequisites:
- Signature verification: cosign CLI
You can verify a catalog's YAML file by using the corresponding bundle (the .sigstore.json file)
present inside the image-catalogs directory.
For example:
cosign verify-blob \
catalog-minimal-trixie.yaml \
--bundle catalog-minimal-trixie.sigstore.json \
--certificate-identity-regexp "^https://github.com/cloudnative-pg/postgres-containers/.github/workflows/catalogs.yml@main" \
--certificate-oidc-issuer "https://token.actions.githubusercontent.com"For full details, please refer to the official documentation.
