update for v4.6.7 and removed centos 8 from docs, examples, (#3228)

and makefile

[sc-14635]

Author: ValClarkson

Makefile

@@ -2,12 +2,12 @@
 # Default values if not already set
 ANSIBLE_VERSION ?= 2.9.*
 PGOROOT ?= $(CURDIR)
-PGO_BASEOS ?= centos8
+PGO_BASEOS ?= ubi8
 PGO_IMAGE_PREFIX ?= crunchydata
 PGO_IMAGE_TAG ?= $(PGO_BASEOS)-$(PGO_VERSION)
-PGO_VERSION ?= 4.6.6
+PGO_VERSION ?= 4.6.7
 PGO_PG_VERSION ?= 13
-PGO_PG_FULLVERSION ?= 13.6
+PGO_PG_FULLVERSION ?= 13.7
 PGO_BACKREST_VERSION ?= 2.31
 PACKAGER ?= yum
 

README.md

@@ -185,7 +185,7 @@ to start as quickly as:
 
 ```shell
 kubectl create namespace pgo
-kubectl apply -f https://raw.githubusercontent.com/CrunchyData/postgres-operator/v4.6.6/installers/kubectl/postgres-operator.yml
+kubectl apply -f https://raw.githubusercontent.com/CrunchyData/postgres-operator/v4.6.7/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=centos8-13.6-4.6.6
+CCP_IMAGE_TAG=ubi8-13.7-4.6.7
 
 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.6-4.6.6
+  CCPImageTag:  ubi8-13.7-4.6.7
   Port:  5432
   PGBadgerPort: 10000
   ExporterPort: 9187
@@ -80,4 +80,4 @@ Storage:
 Pgo:
   Audit:  false
   PGOImagePrefix:  registry.developers.crunchydata.com/crunchydata
-  PGOImageTag:  centos8-4.6.6
+  PGOImageTag:  ubi8-4.6.7

docs/config.toml

@@ -25,14 +25,14 @@ 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.6"
-postgresVersion = "13.6"
-postgresVersion13 = "13.6"
-postgresVersion12 = "12.10"
-postgresVersion11 = "11.15"
-postgresVersion10 = "10.20"
+operatorVersion = "4.6.7"
+postgresVersion = "13.7"
+postgresVersion13 = "13.7"
+postgresVersion12 = "12.11"
+postgresVersion11 = "11.16"
+postgresVersion10 = "10.21"
 postgisVersion = "3.0"
-centosBase = "centos8"
+ubiBase = "ubi8"
 
 [outputs]
 home = [ "HTML", "RSS", "JSON"]

docs/content/Configuration/compatibility.md

@@ -12,6 +12,11 @@ version dependencies between the two projects. Below are the operator releases a
 
 | Operator Release   |      Container Release      | Postgres | PgBackrest Version
 |:----------|:-------------|:------------|:--------------
+| 4.6.7 | 4.6.7 | 13.7 | 2.31 |
+|||12.11|2.31|
+|||11.16|2.31|
+|||10.21|2.31|
+||||
 | 4.6.6 | 4.6.6  | 13.6 | 2.31 |
 |||12.10|2.31|
 |||11.15|2.31|

docs/content/Configuration/pgo-yaml-configuration.md

@@ -16,7 +16,7 @@ The *pgo.yaml* file is broken into major sections as described below:
 |---|---|
 |BasicAuth        | If set to `"true"` will enable Basic Authentication. If set to `"false"`, will allow a valid Operator user to successfully authenticate regardless of the value of the password provided for Basic Authentication. Defaults to `"true".`
 |CCPImagePrefix        |newly created containers will be based on this image prefix (e.g. crunchydata), update this if you require a custom image prefix
-|CCPImageTag        |newly created containers will be based on this image version (e.g. {{< param centosBase >}}-{{< param postgresVersion >}}-{{< param operatorVersion >}}), unless you override it using the --ccp-image-tag command line flag
+|CCPImageTag        |newly created containers will be based on this image version (e.g. {{< param ubiBase >}}-{{< param postgresVersion >}}-{{< param operatorVersion >}}), unless you override it using the --ccp-image-tag command line flag
 |Port        | the PostgreSQL port to use for new containers (e.g. 5432)
 |PGBadgerPort | the port used to connect to pgbadger (e.g. 10000)
 |ExporterPort | the port used to connect to postgres exporter (e.g. 9187)

docs/content/Upgrade/automatedupgrade.md

@@ -127,7 +127,7 @@ pgo upgrade mycluster
 
 If you are using the PostGIS-enabled image (i.e. `crunchy-postgres-gis-ha`) or any other custom images, you will need to add the `--ccp-image-tag`:
 ```    
-pgo upgrade --ccp-image-tag={{< param centosBase >}}-{{< param postgresVersion >}}-{{< param postgisVersion >}}-{{< param operatorVersion >}} mygiscluster
+pgo upgrade --ccp-image-tag={{< param ubiBase >}}-{{< param postgresVersion >}}-{{< param postgisVersion >}}-{{< param operatorVersion >}} mygiscluster
 ```
 Where `{{< param postgresVersion >}}` is the PostgreSQL version, `{{< param postgisVersion >}}` is the PostGIS version and `{{< param operatorVersion >}}` is the PostgreSQL Operator version.
 Please note, no tag validation will be performed and additional steps may be required to upgrade your PostGIS extension implementation. For more information on PostGIS upgrade considerations, please see

docs/content/Upgrade/manual/upgrade35.md

@@ -17,7 +17,7 @@ A major change to this container is that the PostgreSQL process is now managed b
 When creating your new clusters using version {{< param operatorVersion >}} of the PostgreSQL Operator, the `pgo create cluster` command will automatically use the new `crunchy-postgres-ha` image if the image is unspecified. If you are creating a PostGIS enabled cluster, please be sure to use the updated image name and image tag, as with the command:
 
 ```
-pgo create cluster mygiscluster --ccp-image=crunchy-postgres-gis-ha --ccp-image-tag={{< param centosBase >}}-{{< param postgresVersion >}}-{{< param postgisVersion >}}-{{< param operatorVersion >}}
+pgo create cluster mygiscluster --ccp-image=crunchy-postgres-gis-ha --ccp-image-tag={{< param ubiBase >}}-{{< param postgresVersion >}}-{{< param postgisVersion >}}-{{< param operatorVersion >}}
 ```
 Where `{{< param postgresVersion >}}` is the PostgreSQL version, `{{< param postgisVersion >}}` is the PostGIS version and `{{< param operatorVersion >}}` is the PostgreSQL Operator version.
 Please note, no tag validation will be performed and additional steps may be required to upgrade your PostGIS extension implementation. For more information on PostGIS upgrade considerations, please see

docs/content/Upgrade/manual/upgrade4.md

@@ -19,7 +19,7 @@ A major change to this container is that the PostgreSQL process is now managed b
 When creating your new clusters using version {{< param operatorVersion >}} of the PostgreSQL Operator, the `pgo create cluster` command will automatically use the new `crunchy-postgres-ha` image if the image is unspecified. If you are creating a PostGIS enabled cluster, please be sure to use the updated image name and image tag, as with the command:
 
 ```
-pgo create cluster mygiscluster --ccp-image=crunchy-postgres-gis-ha --ccp-image-tag={{< param centosBase >}}-{{< param postgresVersion >}}-{{< param postgisVersion >}}-{{< param operatorVersion >}}
+pgo create cluster mygiscluster --ccp-image=crunchy-postgres-gis-ha --ccp-image-tag={{< param ubiBase >}}-{{< param postgresVersion >}}-{{< param postgisVersion >}}-{{< param operatorVersion >}}
 ```
 Where `{{< param postgresVersion >}}` is the PostgreSQL version, `{{< param postgisVersion >}}` is the PostGIS version and `{{< param operatorVersion >}}` is the PostgreSQL Operator version.
 Please note, no tag validation will be performed and additional steps may be required to upgrade your PostGIS extension implementation. For more information on PostGIS upgrade considerations, please see