Supported releases

This page lists the status, timeline and policy for currently supported releases of CloudNativePG.

We are committed to providing support for the latest minor release, with a dedication to launching a new minor release every two months. Each release remains fully supported until reaching its designated "End of Life" date, as outlined in the support status table for CloudNativePG releases. This includes an additional 3-month assistance window to facilitate seamless upgrade planning.

Supported releases of CloudNativePG include releases that are in the active maintenance window and are patched for security and bug fixes.

Subsequent patch releases on a minor release contain backward-compatible changes only.

Support policy

We produce new builds of CloudNativePG for each commit.

Approximately every two months, we build a minor release and run through several additional tests as well as release qualification. We release patch versions for issues found in supported minor releases.

The various types of releases represent a different product quality level and level of assistance from the CloudNativePG community. For details on the support provided by the community, see What we mean by support.

Type Support level Quality and recommended Use
Development Build No support Dangerous, might not be fully reliable. Useful to experiment with.
Minor Release Support provided until 3 months after the N+1 minor release (ex. 1.23 supported until 3 months after 1.24.0 is released)
Patch Same as the corresponding minor release Users are encouraged to adopt patch releases as soon as they are available for a given release.
Security Patch Same as a patch, however, it doesn't contain any additional code other than the security fix from the previous patch Given the nature of security fixes, users are strongly encouraged to adopt security patches after release.

You can find available releases on the releases page.

You can find high-level more information for each minor and patch release in the release notes.

Naming scheme

Our naming scheme is based on Semantic Versioning 2.0.0 as follows:


Where <minor> is increased for each release, and <patch> counts the number of patches for the current <minor> release. A patch is usually a small change relative to the <minor> release.

Git tags for versions are prepended with v.

Support status of CloudNativePG releases

Version Currently supported Release date End of life Supported Kubernetes versions Tested, but not supported Supported Postgres versions
1.23.x Yes April 24, 2024 ~ October, 2024 1.27, 1.28, 1.29 12 - 16
1.22.x Yes December 21, 2023 July 24, 2024 1.26, 1.27, 1.28 1.29 12 - 16
main No, development only 12 - 16

The list of supported Kubernetes versions in the table depends on what the CloudNativePG maintainers think is reasonable to support and to test.

At the moment, the CloudNativePG community doesn't support or test any additional Kubernetes distribution, like Red Hat OpenShift. This might change in the future and, in that case, that would be reflected in an official policy written by the CloudNativePG maintainers.

Supported PostgreSQL versions

The list of supported Postgres versions in the previous table generally depends on what PostgreSQL versions were supported by the community at the time the minor version of CloudNativePG was released.

See the PostgreSQL Versioning Policy page for more information about supported versions.


Starting from November 9, 2023, Postgres 11 is no longer supported.

We also recommend that you regularly update your PostgreSQL operand images and use the latest minor release for the major version you have in use, as not upgrading is riskier than upgrading. As a result, when opening an issue with an older minor version of PostgreSQL, we might not be able to help you.

Upcoming releases

Version Release date End of life
1.24.0 July 16, 2024 Jan/Feb, 2025
1.25.0 Oct/Nov, 2024 Apr/May, 2025
1.26.0 Feb, 2025 Jul/Aug, 2025


Feature freeze happens one week before the release


Dates in the future are uncertain and might change. This applies to Kubernetes versions, too. Updates and changes on the release schedule will be communicated in the Release updates discussion in the main GitHub repository.

Old releases

Version Release date End of life Compatible Kubernetes versions
1.21.x October 12, 2023 Jun 12, 2024 1.25, 1.26, 1.27, 1.28
1.20.x April 27, 2023 January 21, 2024 1.24, 1.25, 1.26, 1.27
1.19.x February 14, 2023 November 3, 2023 1.23, 1.24, 1.25, 1.26
1.18.x Nov 10, 2022 June 12, 2023 1.23, 1.24, 1.25, 1.26, 1.27
1.17.x September 6, 2022 March 20, 2023 1.22, 1.23, 1.24
1.16.x July 7, 2022 December 21, 2022 1.22, 1.23, 1.24
1.15.x April 21, 2022 October 6, 2022 1.21, 1.22, 1.23

What we mean by support

Our support window is roughly five months for each release branch (latest minor release, plus 3 additional months), given that we produce a new final release every two months.

In the following diagram, release-1.23 is an example of a release branch.

For example, if the latest release is v1.23.0, you can expect a supplementary 3-month support period for the preceding release, v1.22.x.

Only the last patch release of each branch is supported.

------+---------------------------------------------> main (trunk development)
       \             \
        \             \
         \             \             v1.23.0
          \             \            Apr 24, 2024                   ^
           \             \----------+---------------> release-1.23  |
            \                                                       | SUPPORTED
             \                                                      | RELEASES
              \   v1.22.0                                           | = last minor
               \  Dec 21, 2023                                      |   release +
                +-------------------+---------------> release-1.22  |   3 months

We offer two types of support:

Technical support
Technical assistance is offered on a best-effort basis for supported releases only. You can request support from the community on the CloudNativePG Slack (in the #general channel), or using GitHub Discussions.
Security and bug fixes
We backport important bug fixes — including security fixes - to all currently supported releases. Before backporting a patch, we ask ourselves: "Does this backport improve CloudNativePG, bearing in mind that we really value stability for already-released versions?"

If you're looking for professional support, see the Support page in the website. The vendors listed there might provide service level agreements that included extended support timeframes.