@@ -466,7 +466,7 @@ file on the source PostgreSQL instance:
466466host replication streaming_replica all md5
467467` ` `
468468
469- The following manifest creates a new PostgreSQL 16.1 cluster,
469+ The following manifest creates a new PostgreSQL 17.0 cluster,
470470called `target-db`, using the `pg_basebackup` bootstrap method
471471to clone an external PostgreSQL cluster defined as `source-db`
472472(in the `externalClusters` array). As you can see, the `source-db`
@@ -481,7 +481,7 @@ metadata:
481481 name: target-db
482482spec:
483483 instances: 3
484- imageName: ghcr.io/cloudnative-pg/postgresql:16.1
484+ imageName: ghcr.io/cloudnative-pg/postgresql:17.0
485485
486486 bootstrap:
487487 pg_basebackup:
@@ -501,7 +501,7 @@ spec:
501501` ` `
502502
503503All the requirements must be met for the clone operation to work, including
504- the same PostgreSQL version (in our case 16.1 ).
504+ the same PostgreSQL version (in our case 17.0 ).
505505
506506# ### TLS certificate authentication
507507
@@ -516,7 +516,7 @@ in the same Kubernetes cluster.
516516 This example can be easily adapted to cover an instance that resides
517517 outside the Kubernetes cluster.
518518
519- The manifest defines a new PostgreSQL 16.1 cluster called `cluster-clone-tls`,
519+ The manifest defines a new PostgreSQL 17.0 cluster called `cluster-clone-tls`,
520520which is bootstrapped using the `pg_basebackup` method from the `cluster-example`
521521external cluster. The host is identified by the read/write service
522522in the same cluster, while the `streaming_replica` user is authenticated
@@ -531,7 +531,7 @@ metadata:
531531 name: cluster-clone-tls
532532spec:
533533 instances: 3
534- imageName: ghcr.io/cloudnative-pg/postgresql:16.1
534+ imageName: ghcr.io/cloudnative-pg/postgresql:17.0
535535
536536 bootstrap:
537537 pg_basebackup:
0 commit comments