Bump 4.5.0-rc.1

Author: Jonathan S. Katz

Makefile

@@ -9,7 +9,7 @@ PGO_CMD ?= kubectl
 PGO_IMAGE_PREFIX ?= crunchydata
 PGO_IMAGE_TAG ?= $(PGO_BASEOS)-$(PGO_VERSION)
 PGO_OPERATOR_NAMESPACE ?= pgo
-PGO_VERSION ?= 4.5.0-beta.1
+PGO_VERSION ?= 4.5.0-rc.1
 PGO_PG_VERSION ?= 12
 PGO_PG_FULLVERSION ?= 12.4
 PGO_BACKREST_VERSION ?= 2.29

README.md

@@ -161,7 +161,7 @@ Based on your storage settings in your Kubernetes environment, you may be able t
 
 ```shell
 kubectl create namespace pgo
-kubectl apply -f https://raw.githubusercontent.com/CrunchyData/postgres-operator/v4.5.0-beta.1/installers/kubectl/postgres-operator.yml
+kubectl apply -f https://raw.githubusercontent.com/CrunchyData/postgres-operator/v4.5.0-rc.1/installers/kubectl/postgres-operator.yml
 ```
 
 Otherwise, we highly recommend following the instructions from our [Quickstart](https://access.crunchydata.com/documentation/postgres-operator/latest/quickstart/).

bin/push-ccp-to-gcr.sh

@@ -16,7 +16,7 @@
 GCR_IMAGE_PREFIX=gcr.io/crunchy-dev-test
 
 CCP_IMAGE_PREFIX=crunchydata
-CCP_IMAGE_TAG=centos7-12.4-4.5.0-beta.1
+CCP_IMAGE_TAG=centos7-12.4-4.5.0-rc.1
 
 IMAGES=(
 crunchy-prometheus

conf/postgres-operator/pgo.yaml

@@ -2,7 +2,7 @@ Cluster:
   CCPImagePrefix:  registry.developers.crunchydata.com/crunchydata
   Metrics:  false
   Badger:  false
-  CCPImageTag:  centos7-12.4-4.5.0-beta.1
+  CCPImageTag:  centos7-12.4-4.5.0-rc.1
   Port:  5432
   PGBadgerPort: 10000
   ExporterPort: 9187
@@ -82,4 +82,4 @@ Storage:
 Pgo:
   Audit:  false
   PGOImagePrefix:  registry.developers.crunchydata.com/crunchydata
-  PGOImageTag:  centos7-4.5.0-beta.1
+  PGOImageTag:  centos7-4.5.0-rc.1

docs/config.toml

@@ -25,8 +25,9 @@ disableNavChevron = false # set true to hide next/prev chevron, default is false
 highlightClientSide = false # set true to use highlight.pack.js instead of the default hugo chroma highlighter
 menushortcutsnewtab = true # set true to open shortcuts links to a new tab/window
 enableGitInfo = true
-operatorVersion = "4.5.0-beta.1"
+operatorVersion = "4.5.0-rc.1"
 postgresVersion = "12.4"
+postgresVersion13 = "13.0"
 postgresVersion12 = "12.4"
 postgresVersion11 = "11.9"
 postgresVersion10 = "10.14"

docs/content/advanced/crunchy-postgres-exporter.md

@@ -1,6 +1,6 @@
 ---
 title: "Crunchy Postgres Exporter"
-date: 
+date:
 draft: false
 weight: 3
 ---
@@ -23,7 +23,7 @@ can be specified for the API to collect. For an example of a queries.yml file, s
 
 The crunchy-postgres-exporter Docker image contains the following packages (versions vary depending on PostgreSQL version):
 
-* PostgreSQL ({{< param postgresVersion12 >}}, {{< param postgresVersion11 >}}, {{< param postgresVersion10 >}}, {{< param postgresVersion96 >}} and {{< param postgresVersion95 >}})
+* PostgreSQL ({{< param postgresVersion13 >}}, {{< param postgresVersion12 >}}, {{< param postgresVersion11 >}}, {{< param postgresVersion10 >}}, {{< param postgresVersion96 >}} and {{< param postgresVersion95 >}})
 * CentOS7 - publicly available
 * UBI7 - customers only
 * [PostgreSQL Exporter](https://github.com/wrouesnel/postgres_exporter)

docs/content/releases/4.5.0.md

@@ -1,34 +1,30 @@
----
-title: "4.5.0"
-date:
-draft: false
-weight: 70
----
-
 Crunchy Data announces the release of the PostgreSQL Operator 4.5.0 on September XX, 2020.
 
 The PostgreSQL Operator is released in conjunction with the [Crunchy Container Suite](https://github.com/CrunchyData/crunchy-containers/).
 
 The PostgreSQL Operator 4.5.0 release includes the following software versions upgrades:
 
+- Add support for [PostgreSQL 13](https://www.postgresql.org/about/news/2077/).
 - [pgBackRest](https://pgbackrest.org/) is now at version 2.29.
 - [postgres\_exporter](https://github.com/wrouesnel/postgres_exporter) is now at version 0.8.0
 - [pgMonitor](https://github.com/CrunchyData/pgmonitor) support is now at 4.4
 - [pgnodemx](https://github.com/CrunchyData/pgnodemx) is now at version 1.0.1
+- [wal2json](https://github.com/eulerto/wal2json) is now at version 2.3
+- [Patroni](https://patroni.readthedocs.io/) is now at version 2.0.0
 
-Additionally, PostgreSQL Operator 4.5.0 introduces support for the CentOS 8 and UBI 8 base container images. In addition to using the newer operating systems, this enables support for TLS 1.3 when connecting to PostgreSQL. This release also moves to building the containers using [Buildah](https://buildah.io/) 1.14.9 and above, and supports Go 1.15.
+Additionally, PostgreSQL Operator 4.5.0 introduces support for the CentOS 8 and UBI 8 base container images. In addition to using the newer operating systems, this enables support for TLS 1.3 when connecting to PostgreSQL. This release also moves to building the containers using [Buildah](https://buildah.io/) 1.14.9.
 
 The monitoring stack for the PostgreSQL Operator has shifted to use upstream components as opposed to repackaging them. These are specified as part of the [PostgreSQL Operator Installer](https://access.crunchydata.com/documentation/postgres-operator/latest/installation/postgres-operator/). We have tested this release with the following versions of each component:
 
 - Prometheus: 2.20.0
 - Grafana: 6.7.4
 - Alertmanager: 0.21.0
 
-PostgreSQL Operator is tested with Kubernetes 1.15 - 1.18, OpenShift 3.11+, OpenShift 4.4+, Google Kubernetes Engine (GKE), and VMware Enterprise PKS 1.3+.
+PostgreSQL Operator is tested with Kubernetes 1.15 - 1.19, OpenShift 3.11+, OpenShift 4.4+, Google Kubernetes Engine (GKE), Amazon EKS, and VMware Enterprise PKS 1.3+.
 
 ## Major Features
 
-### [PostgreSQL Operator Monitoring](https://crunchydata.github.io/postgres-operator/latest/architecture/monitoring/)
+### PostgreSQL Operator Monitoring
 
 ![PostgreSQL Operator Monitoring](/images/postgresql-monitoring.png)
 
@@ -56,10 +52,6 @@ You can find out how to [install PostgreSQL Operator Monitoring](https://access.
 
 [https://access.crunchydata.com/documentation/postgres-operator/latest/latest/installation/metrics/](https://access.crunchydata.com/documentation/postgres-operator/latest/latest/installation/metrics/)
 
-More information on how the monitoring systems works is available at:
-
-[https://crunchydata.github.io/postgres-operator/latest/architecture/monitoring/](https://crunchydata.github.io/postgres-operator/latest/architecture/monitoring/)
-
 ### Customizing pgBackRest via ConfigMap
 
 [pgBackRest](https://pgbackrest.org/) powers the [disaster recovery](https://access.crunchydata.com/documentation/postgres-operator/latest/architecture/disaster-recovery/) capabilities of PostgreSQL clusters deployed by the PostgreSQL Operator. While the PostgreSQL Operator provides many toggles to customize a pgBackRest configuration, it can be easier to do so directly using the [pgBackRest configuration file format](https://pgbackrest.org/configuration.html).
@@ -129,22 +121,31 @@ To remove an annotation, one follows the format:
 
 ## Changes
 
+- The PostgreSQL Operator now supports the default storage class that is available within a Kubernetes cluster. The installers are updated to use the default storage class by default.
 - The [`pgo restore`](https://access.crunchydata.com/documentation/postgres-operator/latest/pgo-client/reference/pgo_restore/) methodology is changed to mirror the approach taken by `pgo create cluster --restore-from` that was introduced in the previous release. While `pgo restore` will still perform a ["restore in-place"](https://access.crunchydata.com/documentation/postgres-operator/latest/architecture/disaster-recovery/#restores),  it will now take the following actions:
   - Any existing persistent volume claims (PVCs) in a cluster removed.
   - New PVCs are initialized and the data from the PostgreSQL cluster is restored based on the parameters specified in `pgo restore`.
   - Any customizations for the cluster (e.g. custom PostgreSQL configuration) will be available.
   - This also fixes several bugs that were reported with the `pgo restore` functionality, some of which are captured further down in these release notes.
+- Connections to pgBouncer can now be passed along to the default `postgres` database. If you have a pre-existing pgBouncer Deployment, the most convenient way to access this functionality is to redeploy pgBouncer for that PostgreSQL cluster (`pgo delete pgbouncer` + `pgo create pgbouncer`). Suggested by (@lgarcia11).
 - The [Downward API](https://kubernetes.io/docs/tasks/inject-data-application/downward-api-volume-expose-pod-information/) is now available to PostgreSQL instances.
+- The pgBouncer `pgbouncer.ini` and `pg_hba.conf` have been moved from the pgBouncer Secret to a ConfigMap whose name follows the pattern `<clusterName>-pgbouncer-cm`. These are mounted as part of a project volume in conjunction with the current pgBouncer Secret.
 - The `pgo df` command will round values over 1000 up to the next unit type, e.g. `1GiB` instead of `1024MiB`.
 
 ## Fixes
 
 - Ensure that if a PostgreSQL cluster is recreated from a PVC with existing data that it will apply any custom PostgreSQL configuration settings that are specified.
 - Fixed issues with PostgreSQL replica Pods not becoming ready after running `pgo restore`. This fix is a result of the change in methodology for how a restore occurs.
+- The `pgo scaledown` now allows for the removal of replicas that are not actively running.
+- The `pgo scaledown --query` command now shows replicas that may not be in an active state.
 - The pgBackRest URI style defaults to `host` if it is not set.
-- pgBackRest commands can now be executed even if there are multiple pgBackRest Pods available in a Deployment, so long as there is only one "running" pgBackRest Pod.
+- pgBackRest commands can now be executed even if there are multiple pgBackRest Pods available in a Deployment, so long as there is only one "running" pgBackRest Pod. Reported by Rubin Simons (@rubin55).
 - Ensure pgBackRest S3 Secrets can be upgraded from PostgreSQL Operator 4.3.
+- Ensure pgBouncer Port is derived from the cluster's port, not the Operator configuration defaults.
+- External WAL PVCs are only removed for the replica they are targeted for on a scaledown. Reported by (@dakine1111).
 - Return an error if a cluster is not found when using `pgo df` instead of timing out.
 - pgBadger now has a default memory limit of 64Mi, which should help avoid a visit from the OOM killer.
+- The Postgres Exporter now works if it is deployed in a TLS-only environment, i.e. the `--tls-only` flag is set. Reported by (@shuhanfan).
 - Fix `pgo label` when applying multiple labels at once.
 - Fix `pgo create pgorole` so that the expression `--permissions=*` works.
+- The `operator` container will no longer panic if all Deployments are scaled to `0` without using the `pgo update cluster <mycluster> --shutdown` command.

examples/create-by-resource/fromcrd.json

@@ -16,7 +16,7 @@
       "pg-cluster": "fromcrd",
       "pg-pod-anti-affinity": "",
       "pgo-backrest": "true",
-      "pgo-version": "4.5.0-beta.1",
+      "pgo-version": "4.5.0-rc.1",
       "pgouser": "pgoadmin",
       "primary": "true"
     },
@@ -62,7 +62,7 @@
     },
     "backrestResources": {},
     "ccpimage": "crunchy-postgres-ha",
-    "ccpimagetag": "centos7-12.4-4.5.0-beta.1",
+    "ccpimagetag": "centos7-12.4-4.5.0-rc.1",
     "clustername": "fromcrd",
     "customconfig": "",
     "database": "userdb",
@@ -95,7 +95,7 @@
     "userlabels": {
       "crunchy-postgres-exporter": "false",
       "pg-pod-anti-affinity": "",
-      "pgo-version": "4.5.0-beta.1",
+      "pgo-version": "4.5.0-rc.1",
       "pgouser": "pgoadmin",
       "pgo-backrest": "true"
     },

examples/envs.sh

@@ -23,7 +23,7 @@ export PGO_CONF_DIR=$PGOROOT/installers/ansible/roles/pgo-operator/files
 # the version of the Operator you run is set by these vars
 export PGO_IMAGE_PREFIX=registry.developers.crunchydata.com/crunchydata
 export PGO_BASEOS=centos7
-export PGO_VERSION=4.5.0-beta.1
+export PGO_VERSION=4.5.0-rc.1
 export PGO_IMAGE_TAG=$PGO_BASEOS-$PGO_VERSION
 
 # for setting the pgo apiserver port, disabling TLS or not verifying TLS

installers/ansible/README.md

@@ -4,7 +4,7 @@
   <img width="150" src="../../crunchy_logo.png" alt="Crunchy Data"/>
 </p>
 
-Latest Release: 4.5.0-beta.1
+Latest Release: 4.5.0-rc.1
 
 ## General