updated from pg13 to pg14 in the update cluster instructions (CrunchyData#3209)

* updated from pg13 to pg14 in the update cluster instructions

* returned values to prior version to ensure images are present to
run k3d(s) tests

Author: ValClarkson

.github/workflows/test.yaml

@@ -72,9 +72,9 @@ jobs:
       - name: Prefetch container images
         run: |
           {
-            echo '"registry.developers.crunchydata.com/crunchydata/crunchy-postgres:ubi8-13.7-0"'
-            echo '"registry.developers.crunchydata.com/crunchydata/crunchy-pgbackrest:ubi8-2.38-1"'
-            echo '"registry.developers.crunchydata.com/crunchydata/crunchy-pgbouncer:ubi8-1.16-3"'
+            echo '"registry.developers.crunchydata.com/crunchydata/crunchy-postgres:ubi8-13.6-1"'
+            echo '"registry.developers.crunchydata.com/crunchydata/crunchy-pgbackrest:ubi8-2.38-0"'
+            echo '"registry.developers.crunchydata.com/crunchydata/crunchy-pgbouncer:ubi8-1.16-2"'
           } |
           jq --slurp --arg name 'image-prefetch' --argjson labels '{"name":"image-prefetch"}' '{
             apiVersion: "apps/v1", kind: "DaemonSet",

docs/content/tutorial/update-cluster.md

@@ -17,16 +17,16 @@ The Postgres image is referenced using the `spec.image` and looks similar to the
 
 ```
 spec:
-  image: registry.developers.crunchydata.com/crunchydata/crunchy-postgres:centos8-13.4-0
+  image: registry.developers.crunchydata.com/crunchydata/crunchy-postgres:centos8-14.2-0
 ```
 
-Diving into the tag a bit further, you will notice the `13.4-0` portion. This represents the Postgres minor version (`13.4`) and the patch number of the release `0`. If the patch number is incremented (e.g. `13.4-1`), this means that the container is rebuilt, but there are no changes to the Postgres version. If the minor version is incremented (e.g. `13.4-0`), this means that there is a newer bug fix release of Postgres within the container.
+Diving into the tag a bit further, you will notice the `14.2-0` portion. This represents the Postgres minor version (`14.2`) and the patch number of the release `0`. If the patch number is incremented (e.g. `14.2-1`), this means that the container is rebuilt, but there are no changes to the Postgres version. If the minor version is incremented (e.g. `14.2-0`), this means that there is a newer bug fix release of Postgres within the container.
 
 To update the image, you just need to modify the `spec.image` field with the new image reference, e.g.
 
 ```
 spec:
-  image: registry.developers.crunchydata.com/crunchydata/crunchy-postgres:centos8-13.4-1
+  image: registry.developers.crunchydata.com/crunchydata/crunchy-postgres:centos8-14.2-1
 ```
 
 You can apply the changes using `kubectl apply`. Similar to the rolling update example when we [resized the cluster]({{< relref "./resize-cluster.md" >}}), the update is first applied to the Postgres replicas, then a controlled switchover occurs, and the final instance is updated.

internal/controller/postgrescluster/helpers_test.go

@@ -43,9 +43,9 @@ import (
 var (
 	//TODO(tjmoore4): With the new RELATED_IMAGES defaulting behavior, tests could be refactored
 	// to reference those environment variables instead of hard coded image values
-	CrunchyPostgresHAImage = "registry.developers.crunchydata.com/crunchydata/crunchy-postgres:ubi8-13.7-0"
-	CrunchyPGBackRestImage = "registry.developers.crunchydata.com/crunchydata/crunchy-pgbackrest:ubi8-2.38-1"
-	CrunchyPGBouncerImage  = "registry.developers.crunchydata.com/crunchydata/crunchy-pgbouncer:ubi8-1.16-3"
+	CrunchyPostgresHAImage = "registry.developers.crunchydata.com/crunchydata/crunchy-postgres:ubi8-13.6-1"
+	CrunchyPGBackRestImage = "registry.developers.crunchydata.com/crunchydata/crunchy-pgbackrest:ubi8-2.38-0"
+	CrunchyPGBouncerImage  = "registry.developers.crunchydata.com/crunchydata/crunchy-pgbouncer:ubi8-1.16-2"
 )
 
 // Scale extends d according to PGO_TEST_TIMEOUT_SCALE.