EDB Postgres for Kubernetes 1.14.0 release notes v1

Released: 25 Mar 2022

This release of EDB Postgres for Kubernetes includes the following:

FeatureNatively support Google Cloud Storage for backup and recovery, by taking advantage of the features introduced in Barman Cloud 2.19.
FeatureImproved observability of backups through the introduction of the LastBackupSucceeded condition for the Cluster object.
FeatureSupport update of Hot Standby sensitive parameters: max_connections, max_prepared_transactions, max_locks_per_transaction, max_wal_senders, max_worker_processes.
FeatureAdd the Online upgrade in progress phase in the Cluster object to show when an online upgrade of the operator is in progress.
FeatureAbility to inherit an AWS IAM Role as an alternative way to provide credentials for the S3 object storage.
FeatureSupport for Opaque secrets for Pooler’s authQuerySecret and certificates.
FeatureUpdated default PostgreSQL version to 14.2.
FeatureAdd a new command to kubectl cnp plugin named maintenance to set maintenance window to cluster(s) in one or all namespaces across the Kubernetes cluster.
Container imagesLatest PostgreSQL and EDB Postgres Advanced Server containers include Barman Cloud 2.19.
Security fixStronger RBAC enforcement for namespaced operator installations with Operator Lifecycle Manager, including OpenShift. OpenShift users are recommended to update to this version.
Bug fixAllow the instance manager to retry an interrupted pg_rewind by preserving a copy of the original pg_control file.
Bug fixClean up stale PID files before running pg_rewind.
Bug fixForce sorting by key in primary_conninfo to avoid random restarts with PostgreSQL versions prior to 13.
Bug fixPreserve ServiceAccount changes (e.g., labels, annotations) upon reconciliation.
Bug fixDisable enforcement of the imagePullPolicy default value.
Bug fixImprove initDB validation for WAL segment size.
Bug fixProperly handle the targetLSN option when recovering a cluster with the LSN specified.
Bug fixFix custom TLS certificates validation by allowing a certificates chain both in the server and CA certificates.