Container Image Requirements#
The EDB CloudNativePG Cluster operator for Kubernetes is designed to work with any compatible container image of PostgreSQL that complies with the following requirements:
PostgreSQL executables that must be in the path:
initdbpostgrespg_ctlpg_controldatapg_basebackupBarman Cloud executables that must be in the path:
barman-cloud-backupbarman-cloud-backup-deletebarman-cloud-backup-listbarman-cloud-check-wal-archivebarman-cloud-restorebarman-cloud-wal-archivebarman-cloud-wal-restorePGAudit extension installed (optional - only if PGAudit is required in the deployed clusters)
Appropriate locale settings
du(optional, forkubectl cnp status)
Important
Only PostgreSQL versions supported by the PGDG are allowed.
No entry point and/or command is required in the image definition, as EDB CloudNativePG Cluster overrides it with its instance manager.
Warning
Application Container Images will be used by EDB CloudNativePG Cluster in a Primary with multiple/optional Hot Standby Servers Architecture only.
EDB provides and supports public PostgreSQL container images
for EDB CloudNativePG Cluster, and publishes them on quay.io .
Image Tag Requirements#
To ensure the operator makes informed decisions, it must accurately detect the PostgreSQL major version. This detection can occur in two ways:
Utilizing the
majorfield of theimageCatalogRef, if defined.Auto-detecting the major version from the image tag of the
imageNameif not explicitly specified.
For auto-detection to work, the image tag must adhere to a specific format. It should commence with a valid PostgreSQL major version number (e.g., 15.6 or 16), optionally followed by a dot and the patch level.
Following this, the tag can include any character combination valid and accepted in a Docker tag, preceded by a dot, an underscore, or a minus sign.
Examples of accepted image tags:
12.113.3.2.1-113.41415.5-1016.0
Warning
latest is not considered a valid tag for the image.
Note
Image tag requirements do no apply for images defined in a catalog.