Bump v4.6.0-rc.1

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.3
+PGO_VERSION ?= 4.6.0-rc.1
 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.3
+CCP_IMAGE_TAG=centos8-13.1-4.6.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:  centos8-13.1-4.6.0-beta.3
+  CCPImageTag:  centos8-13.1-4.6.0-rc.1
   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.3
+  PGOImageTag:  centos8-4.6.0-rc.1

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.3"
+operatorVersion = "4.6.0-rc.1"
 postgresVersion = "13.1"
 postgresVersion13 = "13.1"
 postgresVersion12 = "13.1"

docs/content/releases/4.6.0.md

@@ -162,6 +162,8 @@ These changes also include overall organization and build performance optimizati
     - `service-type`, which is now represented by the `serviceType` attribute.
     - `NodeLabelKey`/`NodeLabelValue`, which is now replaced by the `nodeAffinity` attribute.
     - `backrest-storage-type`, which is now represented with the `backrestStorageTypes` attribute.
+- The `--labels` flag on `pgo create cluster` is removed and replaced with the `--label`, which can be specified multiple times. The API endpoint for `pgo create cluster` is also modified: labels must now be passed in as a set of key-value pairs. Please see the "Features" section for more details.
+- The API endpoints for `pgo label` and `pgo delete label` is modified to accept a set of key/value pairs for the values of the `--label` flag. The API parameter for this is now called `Labels`.
 The `pgo upgrade` command will properly moved any data you have in these labels into the correct attributes. You can read more about how to use the various CRD attributes in the [Custom Resources](https://access.crunchydata.com/documentation/postgres-operator/latest/custom-resources/) section of the documentation.
 - The `rootsecretname`, `primarysecretname`, and `usersecretname` attributes on the `pgclusters.crunchydata.com` CRD have been removed. Each of these represented managed Secrets. Additionally, if the managed Secrets are not created at cluster creation time, the Operator will now generate these Secrets.
 - The `collectSecretName` attribute on `pgclusters.crunchydata.com` has been removed. The Secret for the metrics collection user is now fully managed by the PostgreSQL Operator.
@@ -193,6 +195,8 @@ 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.
+- `pgo create cluster` now accepts a `--label` flag that can be used to specify one or more custom labels for a PostgreSQL cluster. This replaces the `--labels`flag.
+- `pgo label` and `pgo delete label` can accept a `--label` flag specified multiple times.
 - 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).
 
@@ -233,7 +237,9 @@ Passing in the [`--process-max`](https://pgbackrest.org/command.html#command-arc
 - 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.
+- Generally improvements to initialization of 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).
+- Ensure proper label parsing based on Kubernetes rules and that it is consistently applied across all functionality that uses labels. Reported by José Joye (@jose-joye).
 - 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).

examples/create-by-resource/fromcrd.json

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

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.3
+export PGO_VERSION=4.6.0-rc.1
 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.3`.
+- `imageTag`: The container image tag to use. Defaults to `centos8-13.1-4.6.0-rc.1`.
 - `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.3
+appVersion: 4.6.0-rc.1

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.3" | quote }}
+  ccpimagetag: {{ .Values.imageTag | default "centos8-13.1-4.6.0-rc.1" | quote }}
   clustername: {{ .Values.name | quote }}
   database: {{ .Values.name | quote }}
   {{- if .Values.monitoring }}