Merge pull request #1943 from EnterpriseDB/release/2021-10-15

Author: josh-heyer

advocacy_docs/kubernetes/cloud_native_postgresql/api_reference.mdx

@@ -341,6 +341,8 @@ Name                            | Description
 `certificates                   ` | The configuration for the CA and related certificates, initialized with defaults.                                                                                                  | [CertificatesStatus](#CertificatesStatus)            
 `firstRecoverabilityPoint       ` | The first recoverability point, stored as a date in RFC3339 format                                                                                                                 | string                                               
 `cloudNativePostgresqlCommitHash` | The commit hash number of which this operator running                                                                                                                              | string                                               
+`currentPrimaryTimestamp        ` | The timestamp when the last actual promotion to primary has occurred                                                                                                               | string                                               
+`targetPrimaryTimestamp         ` | The timestamp when the last request for a new primary has occurred                                                                                                                 | string                                               
 
 <a id='ConfigMapKeySelector'></a>
 

advocacy_docs/kubernetes/cloud_native_postgresql/backup_recovery.mdx

@@ -401,9 +401,8 @@ You can also schedule your backups periodically by creating a
 resource named `ScheduledBackup`. The latter is similar to a
 `Backup` but with an added field, called `schedule`.
 
-This field is a [Cron](https://en.wikipedia.org/wiki/Cron) schedule
-specification with a prepended field for seconds. This schedule format
-is the same used in Kubernetes CronJobs.
+This field is a *cron schedule* specification, which follows the same
+[format used in Kubernetes CronJobs](https://pkg.go.dev/github.com/robfig/cron#hdr-CRON_Expression_Format).
 
 This is an example of a scheduled backup:
 
@@ -418,7 +417,20 @@ spec:
     name: pg-backup
 ```
 
-The proposed specification will schedule a backup every day at midnight.
+The above example will schedule a backup every day at midnight.
+
+!!! Hint
+    Backup frequency might impact your recovery time object (RTO) after a
+    disaster which requires a full or Point-In-Time recovery operation. Our
+    advice is that you regularly test your backups by recovering them, and then
+    measuring the time it takes to recover from scratch so that you can refine
+    your RTO predictability. Recovery time is influenced by the size of the
+    base backup and the amount of WAL files that need to fetched from the archive
+    and replayed during recovery (remember that WAL archiving is what enables
+    continuous backup in PostgreSQL!).
+    Based on our experience, a weekly base backup is more than enough for most
+    cases - while it is extremely rare to schedule backups more frequently than once
+    a day.
 
 ScheduledBackups can be suspended if needed by setting `.spec.suspend: true`,
 this will stop any new backup to be scheduled as long as the option is set to false.

advocacy_docs/kubernetes/cloud_native_postgresql/cloud_setup.mdx

@@ -94,9 +94,23 @@ Please refer to the
 ["Platform Compatibility"](https://www.enterprisedb.com/product-compatibility#cnp)
 page from the EDB website for a list of the currently supported Kubernetes distributions.
 
-## Supported PostgreSQL versions
+### Multiple architectures
 
-PostgreSQL and EDB Postgres Advanced 13, 12, 11 and 10 are currently supported.
+The Cloud Native PostgreSQL Operator container images support the multi-arch
+format for the following platforms: `linux/amd64`, `linux/arm64`,
+`linux/ppc64le`, `linux/s390x`.
+
+!!! Warning
+    Cloud Native PostgreSQL requires that all nodes in a Kubernetes cluster have the
+    same CPU architecture, thus a hybrid CPU architecture Kubernetes cluster is not
+    supported.
+
+## Supported Postgres versions
+
+The following versions of Postgres are currently supported:
+
+- PostgreSQL 13, 12, 11 and 10 (`linux/amd64`)
+- EDB Postgres Advanced 13, 12, 11 and 10 (`linux/amd64`, `linux/ppc64le`, `linux/s390x`)
 
 ## Main features
 
@@ -125,6 +139,7 @@ PostgreSQL and EDB Postgres Advanced 13, 12, 11 and 10 are currently supported.
 * Standard output logging of PostgreSQL error messages in JSON format
 * Support for the `restricted` security context constraint (SCC) in Red Hat OpenShift
 * `cnp` plugin for `kubectl`
+* Multi-arch format container images
 
 ## About this guide
 

advocacy_docs/kubernetes/cloud_native_postgresql/index.mdx

@@ -11,12 +11,12 @@ product: 'Cloud Native Operator'
 The operator can be installed like any other resource in Kubernetes,
 through a YAML manifest applied via `kubectl`.
 
-You can install the [latest operator manifest](https://get.enterprisedb.io/cnp/postgresql-operator-1.9.1.yaml)
+You can install the [latest operator manifest](https://get.enterprisedb.io/cnp/postgresql-operator-1.9.2.yaml)
 as follows:
 
 ```sh
 kubectl apply -f \
-  https://get.enterprisedb.io/cnp/postgresql-operator-1.9.1.yaml
+  https://get.enterprisedb.io/cnp/postgresql-operator-1.9.2.yaml
 ```
 
 Once you have run the `kubectl` command, Cloud Native PostgreSQL will be installed in your Kubernetes cluster.

advocacy_docs/kubernetes/cloud_native_postgresql/installation_upgrade.mdx

@@ -258,16 +258,18 @@ All logs that are produced by the operator and its instances are in JSON
 format, with `logger` set accordingly to the process that produced them.
 Therefore, all the possible `logger` values are the following ones:
 
-- `barman-cloud-wal-archive`
-- `barman-cloud-wal-restore`
-- `edb_audit`
-- `initdb`
-- `pg_basebackup`
-- `pg_controldata`
-- `pg_ctl`
-- `pg_rewind`
-- `pgaudit`
-- `postgres`
+- `barman-cloud-wal-archive`: from `barman-cloud-wal-archive` directly
+- `barman-cloud-wal-restore`: from `barman-cloud-wal-restore` directly
+- `edb_audit`: from the EDB Audit extension
+- `initdb`: from running `initdb`
+- `pg_basebackup`: from running `pg_basebackup`
+- `pg_controldata`: from running `pg_controldata`
+- `pg_ctl`: from running any `pg_ctl` subcommand
+- `pg_rewind`: from running `pg_rewind`
+- `pgaudit`: from PGAudit extension
+- `postgres`: from the `postgres` instance (having `msg` different than `record`)
+- `wal-archive`: from the `wal-archive` subcommand of the instance manager
+- `wal-restore`: from the `wal-restore` subcommand of the instance manager
 
 Except for `postgres` and `edb_audit` that have the aforementioned structures,
 all other possible values just have `msg` set to the escaped message that is

advocacy_docs/kubernetes/cloud_native_postgresql/logging.mdx

@@ -6,6 +6,23 @@ product: 'Cloud Native Operator'
 
 History of user-visible changes for Cloud Native PostgreSQL.
 
+## Version 1.9.2
+
+**Release date:** 15 October 2021
+
+Features:
+
+- Enhance JSON log with two new loggers: `wal-archive` for PostgreSQL's
+  `archive_command`, and `wal-restore` for `restore_command` in a standby
+
+Fixes:
+
+- Enable WAL archiving during the standby promotion (prevented `.history` files
+  from being archived)
+- Pass the `--cloud-provider` option to Barman Cloud tools only when using
+  Barman 2.13 or higher to avoid errors with older operands
+- Wait for the pod of the primary to be ready before triggering a backup
+
 ## Version 1.9.1
 
 **Release date:** 30 September 2021