feat: update default PostgreSQL version to 17.1

Signed-off-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>

Author: postgres-versions-updater

.github/pg_versions.json

@@ -1,26 +1,26 @@
 {
   "17": [
-    "17.0",
-    "17.0-20"
+    "17.1",
+    "17.0"
   ],
   "16": [
-    "16.4",
-    "16.3"
+    "16.5",
+    "16.4"
   ],
   "15": [
-    "15.8",
-    "15.7"
+    "15.9",
+    "15.8"
   ],
   "14": [
-    "14.13",
-    "14.12"
+    "14.14",
+    "14.13"
   ],
   "13": [
-    "13.16",
-    "13.15"
+    "13.17",
+    "13.16"
   ],
   "12": [
-    "12.20",
-    "12.19"
+    "12.21",
+    "12.20"
   ]
 }

docs/src/bootstrap.md

@@ -519,7 +519,7 @@ file on the source PostgreSQL instance:
 host replication streaming_replica all md5
 ```
 
-The following manifest creates a new PostgreSQL 17.0 cluster,
+The following manifest creates a new PostgreSQL 17.1 cluster,
 called `target-db`, using the `pg_basebackup` bootstrap method
 to clone an external PostgreSQL cluster defined as `source-db`
 (in the `externalClusters` array). As you can see, the `source-db`
@@ -534,7 +534,7 @@ metadata:
   name: target-db
 spec:
   instances: 3
-  imageName: ghcr.io/cloudnative-pg/postgresql:17.0
+  imageName: ghcr.io/cloudnative-pg/postgresql:17.1
 
   bootstrap:
     pg_basebackup:
@@ -554,7 +554,7 @@ spec:
 ```
 
 All the requirements must be met for the clone operation to work, including
-the same PostgreSQL version (in our case 17.0).
+the same PostgreSQL version (in our case 17.1).
 
 #### TLS certificate authentication
 
@@ -569,7 +569,7 @@ in the same Kubernetes cluster.
     This example can be easily adapted to cover an instance that resides
     outside the Kubernetes cluster.
 
-The manifest defines a new PostgreSQL 17.0 cluster called `cluster-clone-tls`,
+The manifest defines a new PostgreSQL 17.1 cluster called `cluster-clone-tls`,
 which is bootstrapped using the `pg_basebackup` method from the `cluster-example`
 external cluster. The host is identified by the read/write service
 in the same cluster, while the `streaming_replica` user is authenticated
@@ -584,7 +584,7 @@ metadata:
   name: cluster-clone-tls
 spec:
   instances: 3
-  imageName: ghcr.io/cloudnative-pg/postgresql:17.0
+  imageName: ghcr.io/cloudnative-pg/postgresql:17.1
 
   bootstrap:
     pg_basebackup:

docs/src/declarative_hibernation.md

@@ -58,7 +58,7 @@ $ kubectl cnpg status <cluster-name>
 Cluster Summary
 Name:              cluster-example
 Namespace:         default
-PostgreSQL Image:  ghcr.io/cloudnative-pg/postgresql:17.0
+PostgreSQL Image:  ghcr.io/cloudnative-pg/postgresql:17.1
 Primary instance:  cluster-example-2
 Status:            Cluster in healthy state 
 Instances:         3

docs/src/image_catalog.md

@@ -32,7 +32,7 @@ spec:
     - major: 15
       image: ghcr.io/cloudnative-pg/postgresql:15.6
     - major: 16
-      image: ghcr.io/cloudnative-pg/postgresql:17.0
+      image: ghcr.io/cloudnative-pg/postgresql:17.1
 ```
 
 **Example of a Cluster-Wide Catalog using `ClusterImageCatalog` Resource:**
@@ -47,7 +47,7 @@ spec:
     - major: 15
       image: ghcr.io/cloudnative-pg/postgresql:15.6
     - major: 16
-      image: ghcr.io/cloudnative-pg/postgresql:17.0
+      image: ghcr.io/cloudnative-pg/postgresql:17.1
 ```
 
 A `Cluster` resource has the flexibility to reference either an `ImageCatalog`

docs/src/kubectl-plugin.md

@@ -1005,7 +1005,7 @@ it from the actual pod. This means that you will be using the `postgres` user.
 ```shell
 kubectl cnpg psql cluster-example
 
-psql (17.0 (Debian 17.0-1.pgdg110+1))
+psql (17.1 (Debian 17.1-1.pgdg110+1))
 Type "help" for help.
 
 postgres=#
@@ -1016,7 +1016,7 @@ select to work against a replica by using the `--replica` option:
 
 ```shell
 kubectl cnpg psql --replica cluster-example
-psql (17.0 (Debian 17.0-1.pgdg110+1))
+psql (17.1 (Debian 17.1-1.pgdg110+1))
 
 Type "help" for help.
 

docs/src/monitoring.md

@@ -217,7 +217,7 @@ cnpg_collector_up{cluster="cluster-example"} 1
 
 # HELP cnpg_collector_postgres_version Postgres version
 # TYPE cnpg_collector_postgres_version gauge
-cnpg_collector_postgres_version{cluster="cluster-example",full="17.0"} 17.0
+cnpg_collector_postgres_version{cluster="cluster-example",full="17.1"} 17.1
 
 # HELP cnpg_collector_last_failed_backup_timestamp The last failed backup as a unix timestamp
 # TYPE cnpg_collector_last_failed_backup_timestamp gauge

docs/src/postgis.md

@@ -100,7 +100,7 @@ values from the ones in this document):
 ```console
 $ kubectl exec -ti postgis-example-1 -- psql app
 Defaulted container "postgres" out of: postgres, bootstrap-controller (init)
-psql (17.0 (Debian 17.0-1.pgdg110+1))
+psql (17.1 (Debian 17.1-1.pgdg110+1))
 Type "help" for help.
 
 app=# SELECT * FROM pg_available_extensions WHERE name ~ '^postgis' ORDER BY 1;

docs/src/samples/cluster-example-full.yaml

@@ -35,7 +35,7 @@ metadata:
   name: cluster-example-full
 spec:
   description: "Example of cluster"
-  imageName: ghcr.io/cloudnative-pg/postgresql:17.0
+  imageName: ghcr.io/cloudnative-pg/postgresql:17.1
   # imagePullSecret is only required if the images are located in a private registry
   # imagePullSecrets:
   #   - name: private_registry_access

docs/src/scheduling.md

@@ -40,7 +40,7 @@ metadata:
   name: cluster-example
 spec:
   instances: 3
-  imageName: ghcr.io/cloudnative-pg/postgresql:17.0
+  imageName: ghcr.io/cloudnative-pg/postgresql:17.1
 
   affinity:
     enablePodAntiAffinity: true # Default value

docs/src/ssl_connections.md

@@ -173,7 +173,7 @@ Output:
                                         version
 --------------------------------------------------------------------------------------
 ------------------
-PostgreSQL 17.0 on x86_64-pc-linux-gnu, compiled by gcc (GCC) 8.3.1 20191121 (Red Hat
+PostgreSQL 17.1 on x86_64-pc-linux-gnu, compiled by gcc (GCC) 8.3.1 20191121 (Red Hat
 8.3.1-5), 64-bit
 (1 row)
 ```