Six years ago, on January 2, 2019, we tagged the 1.0 release of Crunchy Postgres via Automation (then known as Crunchy HA). Originally a set of Ansible roles, the product grew and morphed into the Ansible collection that it is today over the course of fourteen major releases (in the 1.x line) with contributions from a dozen individuals. And now, with the release of 1.15-17 on Mar 7th, the 1.x line is officially on life support as we phase it out and move customers to our 2.x line.
On Thursday, Feb 13th, the PostgreSQL Global Development Group (PGDG) released their regularly scheduled minor releases of PostgreSQL: 17.3, 16.7, 15.11, 14.16, and 13.19. These releases, among other bugfixes, resolved a CVE within PostgreSQL, so a sense of urgency in releasing them to our customers was bred. This, in turn, kicked off a flurry of activity within Crunchy as we readied Crunchy Postgres via Automation (CPA) for release to ship these new PostgreSQL releases. As we dove into the release process and began our internal testing, word came down from PGDG that the CVE fix was flawed and new PostgreSQL releases would be forthcoming.
Up next on the list of changes coming soon to Crunchy Postgres via Automation (CPA), Patroni 3.x! If you want to know what else is ‘coming soon’, you can catch up here.
We’re back today with more ‘insider info’ on upcoming changes to Crunchy Postgres via Automation (CPA). If you missed any of the prior posts, you can catch up here. We recently committed support for HAProxy 3.0.x into development and changed our default HAProxy configuration around to accommodate the version bump.
Continuing the Crunchy Postgres via Automation (CPA) blog series, we’re back today with another ‘Coming Soon’ entry, where we discuss items that have been merged into development and will appear in a future release. This time around, we’re adding a new supported OS platform, dropping an existing OS platform, and raising the minimal version of ansible-core.
