Bump v4.6.0-beta.3

Author: Jonathan S. Katz

Makefile

@@ -5,7 +5,7 @@ PGOROOT ?= $(CURDIR)
 PGO_BASEOS ?= centos8
 PGO_IMAGE_PREFIX ?= crunchydata
 PGO_IMAGE_TAG ?= $(PGO_BASEOS)-$(PGO_VERSION)
-PGO_VERSION ?= 4.6.0-beta.2
+PGO_VERSION ?= 4.6.0-beta.3
 PGO_PG_VERSION ?= 13
 PGO_PG_FULLVERSION ?= 13.1
 PGO_BACKREST_VERSION ?= 2.31

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=centos8-13.1-4.6.0-beta.2
+CCP_IMAGE_TAG=centos8-13.1-4.6.0-beta.3
 
 IMAGES=(
 crunchy-prometheus

conf/postgres-operator/pgo.yaml

@@ -2,7 +2,7 @@ Cluster:
   CCPImagePrefix:  registry.developers.crunchydata.com/crunchydata
   Metrics:  false
   Badger:  false
-  CCPImageTag:  centos8-13.1-4.6.0-beta.2
+  CCPImageTag:  centos8-13.1-4.6.0-beta.3
   Port:  5432
   PGBadgerPort: 10000
   ExporterPort: 9187
@@ -81,4 +81,4 @@ Storage:
 Pgo:
   Audit:  false
   PGOImagePrefix:  registry.developers.crunchydata.com/crunchydata
-  PGOImageTag:  centos8-4.6.0-beta.2
+  PGOImageTag:  centos8-4.6.0-beta.3

docs/config.toml

@@ -25,7 +25,7 @@ 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.6.0-beta.2"
+operatorVersion = "4.6.0-beta.3"
 postgresVersion = "13.1"
 postgresVersion13 = "13.1"
 postgresVersion12 = "13.1"

docs/content/releases/4.6.0.md

@@ -19,6 +19,7 @@ The PostgreSQL Operator 4.6.0 release includes the following software versions u
 - [pgBackRest](https://pgbackrest.org/) is now at version 2.31.
 - [pgnodemx](https://github.com/CrunchyData/pgnodemx) is now at version 1.0.3
 - [Patroni](https://patroni.readthedocs.io/) is now at version 2.0.1
+- [pgBadger](https://github.com/darold/pgbadger) is now at 11.4
 
 The monitoring stack for the PostgreSQL Operator uses 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:
 
@@ -193,6 +194,7 @@ Passing in the [`--process-max`](https://pgbackrest.org/command.html#command-arc
 - `pgo restore` will now first attempt a [pgBackRest delta restore](https://pgbackrest.org/user-guide.html#restore/option-delta), which can significantly speed up the restore time for large databases. Passing in the [`--process-max`](https://pgbackrest.org/command.html#command-archive-get/category-general/option-process-max) option to `--backup-opts` can help speed up the restore process based upon the amount of CPU you have available.
 - A pgBackRest backup can now be deleted with `pgo delete backup`. A backup name must be specified with the `--target` flag. Please refer to the [documentation](https://access.crunchydata.com/documentation/postgres-operator/latest/tutorial/disaster-recovery/#deleting-a-backup) for how to use this command.
 - pgBadger can now be enabled/disabled during the lifetime of a PostgreSQL cluster using the `pgo update --enable-pgbadger` and `pgo update --disable-pgbadger` flag. This can also be modified directly on a custom resource.
+- Managed PostgreSQL system accounts and now have their credentials set and rotated with `pgo update user` by including the `--set-system-account-password` flag. Suggested by (@srinathganesh).
 
 ## Changes
 
@@ -205,13 +207,16 @@ Passing in the [`--process-max`](https://pgbackrest.org/command.html#command-arc
 - The `pgo failover` command now works without specifying a target: the candidate to fail over to will be automatically selected.
 - For clusters that have no healthy instances, `pgo failover` can now force a promotion using the `--force` flag. A `--target` flag must also be specified when using `--force`.
 - If a predefined custom ConfigMap for a PostgreSQL cluster (`-pgha-config`) is detected at bootstrap time, the Operator will ensure it properly initializes the cluster.
+- Deleting a `pgclusters.crunchydata.com` custom resource will now properly delete a PostgreSQL cluster. If the `pgclusters.crunchydata.com` custom resource has the annotations `keep-backups` or `keep-data`, it will keep the backups or keep the PostgreSQL data directory respectively. Reported by Leo Khomenko (@lkhomenk).
 - PostgreSQL JIT compilation is explicitly disabled on new cluster creation. This prevents a memory leak that has been observed on queries coming from the metrics exporter.
 - The credentials for the metrics collection user are now available with `pgo show user --show-system-accounts`.
 - The default user for executing scheduled SQL policies is now the Postgres superuser, instead of the replication user.
 - Add the `--no-prompt` flag to `pgo upgrade`. The mechanism to disable the prompt verification was already in place, but the flag was not exposed. Reported by (@devopsevd).
 - Remove certain characters that causes issues in shell environments from consideration when using the random password generator, which is used to create default passwords or with `--rotate-password`.
+- Allow for the `--link-map` attribute for a pgBackRest option, which can help with the restore of an existing cluster to a new cluster that adds an external WAL volume.
 - Remove the long deprecated `archivestorage` attribute from the `pgclusters.crunchydata.com` custom resource definition. As this attribute is not used at all, this should have no effect.
 - The `ArchiveMode` parameter is now removed from the configuration. This had been fully deprecated for awhile.
+- Add an explicit size limit of `64Mi` for the `pgBadger` ephemeral storage mount. Additionally, remove the ephemeral storage mount for the `/recover` mount point as that is not used. Reported by Pierre-Marie Petit (@pmpetit).
 - New PostgreSQL Operator deployments will now generate ECDSA keys (P-256, SHA384) for use by the API server.
 
 ## Fixes
@@ -227,9 +232,12 @@ Passing in the [`--process-max`](https://pgbackrest.org/command.html#command-arc
 - Fix syntax in recovery check command which could lead to failures when manually promoting a standby cluster. Reported by (@SockenSalat).
 - Fix potential race condition that could lead to a crash in the Operator boot when an error is issued around loading the `pgo-config` ConfigMap. Reported by Aleksander Roszig (@AleksanderRoszig).
 - Do not trigger a backup if a standby cluster fails over. Reported by (@aprilito1965).
+- Ensure pgBouncer Secret is created when adding it to a standby cluster.
 - Remove legacy `defaultMode` setting on the volume instructions for the pgBackRest repo Secret as the `readOnly` setting is used on the mount itself. Reported by (@szhang1).
 - The logger no longer defaults to using a log level of `DEBUG`.
 - Autofailover is no longer disabled when an `rmdata` Job is run, enabling a clean database shutdown process when deleting a PostgreSQL cluster.
+- Allow for `Restart` API server permission to be explicitly set. Reported by Aleksander Roszig (@AleksanderRoszig).
 - Update `pgo-target` permissions to match expectations for modern Kubernetes versions.
 - Major upgrade container now includes references for `pgnodemx`.
 - During a major upgrade, ensure permissions are correct on the old data directory before running `pg_upgrade`.
+- The metrics stack installer is fixed to work in environments that may not have connectivity to the Internet ("air gapped"). Reported by (@eliranw).

examples/create-by-resource/fromcrd.json

@@ -10,7 +10,7 @@
       "deployment-name": "fromcrd",
       "name": "fromcrd",
       "pg-cluster": "fromcrd",
-      "pgo-version": "4.6.0-beta.2",
+      "pgo-version": "4.6.0-beta.3",
       "pgouser": "pgoadmin"
     },
     "name": "fromcrd",
@@ -45,7 +45,7 @@
       "supplementalgroups": ""
     },
     "ccpimage": "crunchy-postgres-ha",
-    "ccpimagetag": "centos8-13.1-4.6.0-beta.2",
+    "ccpimagetag": "centos8-13.1-4.6.0-beta.3",
     "clustername": "fromcrd",
     "database": "userdb",
     "exporterport": "9187",
@@ -60,7 +60,7 @@
     "port": "5432",
     "user": "testuser",
     "userlabels": {
-      "pgo-version": "4.6.0-beta.2"
+      "pgo-version": "4.6.0-beta.3"
     }
   }
 }

examples/envs.sh

@@ -20,7 +20,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=centos8
-export PGO_VERSION=4.6.0-beta.2
+export PGO_VERSION=4.6.0-beta.3
 export PGO_IMAGE_TAG=$PGO_BASEOS-$PGO_VERSION
 
 # for setting the pgo apiserver port, disabling TLS or not verifying TLS

examples/helm/README.md

@@ -64,7 +64,7 @@ The following values can also be set:
 - `ha`: Whether or not to deploy a high availability PostgreSQL cluster. Can be either `true` or `false`, defaults to `false`.
 - `imagePrefix`: The prefix of the container images to use for this PostgreSQL cluster. Default to `registry.developers.crunchydata.com/crunchydata`.
 - `image`: The name of the container image to use for the PostgreSQL cluster. Defaults to `crunchy-postgres-ha`.
-- `imageTag`: The container image tag to use. Defaults to `centos8-13.1-4.6.0-beta.2`.
+- `imageTag`: The container image tag to use. Defaults to `centos8-13.1-4.6.0-beta.3`.
 - `memory`: The memory limit for the PostgreSQL cluster. Follows standard Kubernetes formatting.
 - `monitoring`: Whether or not to enable monitoring / metrics collection for this PostgreSQL instance. Can either be `true` or `false`, defaults to `false`.
 

examples/helm/postgres/Chart.yaml

@@ -20,4 +20,4 @@ version: 0.2.0
 # This is the version number of the application being deployed. This version number should be
 # incremented each time you make changes to the application. Versions are not expected to
 # follow Semantic Versioning. They should reflect the version the application is using.
-appVersion: 4.6.0-beta.2
+appVersion: 4.6.0-beta.3

examples/helm/postgres/templates/pgcluster.yaml

@@ -28,7 +28,7 @@ spec:
     storagetype: dynamic
   ccpimage: {{ .Values.image | default "crunchy-postgres-ha" | quote }}
   ccpimageprefix: {{ .Values.imagePrefix | default "registry.developers.crunchydata.com/crunchydata" | quote }}
-  ccpimagetag: {{ .Values.imageTag | default "centos8-13.1-4.6.0-beta.2" | quote }}
+  ccpimagetag: {{ .Values.imageTag | default "centos8-13.1-4.6.0-beta.3" | quote }}
   clustername: {{ .Values.name | quote }}
   database: {{ .Values.name | quote }}
   {{- if .Values.monitoring }}