Crunchy Postgres for Kubernetes 5.3 Release
We are excited to announce the release of Crunchy Postgres for Kubernetes version 5.3. We have been hard at work on a lot of new features that we cannot wait to get into your hands. You can get started on version 5.3 from our Developer Portal or the getting started tutorial. We have decided to highlight a few of our favorite new features and changes today.
Hot off the Presses: Postgres 15 and Kubernetes 1.25
With the latest release of Crunchy Postgres for Kubernetes, we are excited to now natively support Postgres 15. Please note that TimescaleDB and pgAdmin 4 are not currently supported for use with Postgres 15. We are hard at work enabling that functionality for Crunchy Postgres for Kubernetes.
We are also excited to announce that Crunchy Postgres for Kubernetes now offers
support for Kubernetes 1.25. Be sure to check your apps’ usage of CronJob,
PodDisruptionBudget, or PodSecurityPolicy before upgrading; some of these
API versions have been removed
in Kubernetes 1.25.
Some of the notable updates in Kubernetes 1.25 that Crunchy Postgres for Kubernetes now supports include:
- Pod Security Admission is stable and Crunchy Postgres for Kubernetes is generally compliant with its baseline policy. It is also compliant with the restricted policy in OpenShift.
- cgroup v2 is stable and works with the bundled pgMonitor v4.8.0 container metrics.
TLS for Exporter
In our ongoing quest to ensure that Crunchy Postgres for Kubernetes remains the default for securely and safely managing Postgres in Kubernetes, we are hard at work to enable safe and sane defaults and settings everywhere we can. We are excited to announce that in Crunchy Postgres for Kubernetes 5.3 you can now enable full TLS for the Postgres Exporter, the tool that exports metrics from the Postgres pods.
Helm Charts
We know a lot of our users like using Helm charts to install Crunchy Postgres for Kubernetes and we are excited to announce that we are now hosting install charts for Crunchy Postgres for Kubernetes 5.3 in our own OCI registry. You can find instructions for using these charts here.
$ helm show chart oci://registry.developers.crunchydata.com/crunchydata/pgo
Pulled: registry.developers.crunchydata.com/crunchydata/pgo:5.3.0
Digest: sha256:7f50f74b0bb4fde32348af87cc740b79ed7be965f90002bcb2425e27fb02a9e3
apiVersion: v2
appVersion: 5.3.0
description: Installer for PGO, the open source Postgres Operator from Crunchy Data
name: pgo
type: application
version: 5.3.0
$ helm install oci://registry.developers.crunchydata.com/crunchydata/pgo
Pulled: registry.developers.crunchydata.com/crunchydata/pgo:5.3.0
IPv6 for pgBackRest
We are excited to announce that IPv6 is now supported for pgBackRest. Users can now successfully deploy Postgres clusters to Kubernetes environments that are configured for IPv6 only! You can find directions for setting that up in the Backup Configuration section of the docs.
Open Source Contributions
Of course a large thank you should go out to our Open Source contributors who help make the Postgres Operator better for everyone. During the last quarter these are the highlights of their contributions:
- JIT is now explicitly disabled for the monitoring user, allowing users to opt-into using JIT elsewhere in the database without impacting exporter functionality. Contributed by Kirill Petrov (@chobostar).
- PGO now logs both stdout and stderr when running a SQL file referenced via spec.databaseInitSQL during database initialization. Contributed by Jeff Martin (@jmartin127).
- Limit the monitoring user to local connections using SCRAM authentication. Contributed by Scott Zelenka (@szelenka)
- Skip a scheduled backup when the prior one is still running. Contributed by Scott Zelenka (@szelenka)
If you would like to lend a hand with PGO development, get started by reviewing the contributing guidelines.
And More…
We are very excited to bring you this next version of Crunchy Postgres for Kubernetes. This is just a sampling of the new features and fixes that we have shipped with this version. We hope that you enjoy using it, and as always we value our community's feedback. The full feature notes are available in our documentation.
