Revisions 462, 463¶
A new revision of Charmed PostgreSQL for Kubernetes has been published in the 14/stable channel.
What’s changed¶
This section outlines the most important highlights, features and bug fixes in this release.
Upgraded PostgreSQL from v.14.12 → v.14.13
Check the official PostgreSQL release notes
Added timeline management to point-in-time recovery (PITR) ( #716 ) (DPE-5581 )
Observability stack (COS) improvements
Features¶
S3 backups improvements ( #750 )
Removed patching of private ops class. ( #692 )
Switched charm libs from
tempo_k8stotempo_coordinator_k8sand test relay support of tracing traffic throughgrafana-agent-k8s( #725 )Added check for low storage space on pgdata volume ( #685 ) (DPE-5301 )
Re-enabled log forwarding ( #671 )
Added pgBackRest logrotate configuration ( #722 ) (DPE-5600 )
Added TLS flag + CA to relation databag ( #719 ) (DPE-5484 )
Added warning logs to Patroni reinitialisation ( #753 ) (DPE-5712 )
Split off new interface client app tests ( #761 )
Temporarily disable log forwarding ( #757 )
Changed owner of functions, procedures and aggregates ( #773 )
Only update tls flags on leader ( #770 )
Bug fixes¶
Fixed PITR backup test instabilities ( #690 )
Fixed some
postgresql.confparameters for hardening ( #702 ) (DPE-5511 )Fixed event deferring issue with missing S3 relation ( #762 ) (DPE-5934 )
Fixed connection rejection rule in
pg_hba.conf( #751 ) (DPE-5689 )
Full Changelog: https://github.com/canonical/postgresql-k8s-operator/compare/rev444…rev462
Known limitations¶
Juju 3.6.1+ is required for consistent usage of Terraform-Provider-Juju (more details here ).
Requirements¶
The minimum Juju version required to reliably operate all features in this release is v.3.6.1.
See the system requirements for more details about Juju versions and other software and hardware prerequisites.