EDB Postgres for Kubernetes 1.4.0 release notes v1
We are in the process of migrating the documentation from the previous EDB Postgres for Kubernetes name to the new EDB CloudNativePG Cluster name. You may see references to both names in this documentation.
Released: 18 May 2021
This release of EDB Postgres for Kubernetes includes the following:
| Type | Description |
|---|---|
| Feature | Standard output logging of PostgreSQL error messages in JSON format. |
| Feature | Provide a basic set of PostgreSQL metrics for the Prometheus exporter. |
| Feature | Add the restart command to the cnp plugin for kubectl to restart the pods of a given PostgreSQL cluster in a rollout fashion. |
| Security fix | Set readOnlyRootFilesystem security context for pods. |
| Change | IMPORTANT: If you have previously deployed the Cloud Native PostgreSQL operator using the YAML manifest, you must delete the existing operator deployment before installing the new version. This is required to avoid conflicts with other Kubernetes API's due to a change in labels and label selectors being directly managed by the operator. Please refer to the Cloud Native PostgreSQL documentation for additional detail on upgrading to 1.4.0. |
| Change | Fix the labels that are automatically defined by the operator, renaming them from control-plane: controller-manager to app.kubernetes.io/name: cloud-native-postgresql. |
| Change | Assign the metrics name to the TCP port for the Prometheus exporter. |
| Change | Set cnp_metrics_exporter as the application_name to the metrics exporter connection in PostgreSQL. |
| Change | When available, use the application database for monitoring queries of the Prometheus exporter instead of the postgres database. |
| Documentation fixes | Customization of monitoring queries. |
| Documentation fixes | Operator upgrade instructions. |
| Bug fix | Avoid using -R when calling pg_basebackup. |
| Bug fix | Remove stack trace from error log when getting the status. |