@@ -779,7 +779,7 @@ file on the source PostgreSQL instance:
779
779
host replication streaming_replica all md5
780
780
` ` `
781
781
782
- The following manifest creates a new PostgreSQL 15.0 cluster,
782
+ The following manifest creates a new PostgreSQL 15.1 cluster,
783
783
called `target-db`, using the `pg_basebackup` bootstrap method
784
784
to clone an external PostgreSQL cluster defined as `source-db`
785
785
(in the `externalClusters` array). As you can see, the `source-db`
@@ -794,7 +794,7 @@ metadata:
794
794
name: target-db
795
795
spec:
796
796
instances: 3
797
- imageName: ghcr.io/cloudnative-pg/postgresql:15.0
797
+ imageName: ghcr.io/cloudnative-pg/postgresql:15.1
798
798
799
799
bootstrap:
800
800
pg_basebackup:
@@ -814,7 +814,7 @@ spec:
814
814
` ` `
815
815
816
816
All the requirements must be met for the clone operation to work, including
817
- the same PostgreSQL version (in our case 15.0 ).
817
+ the same PostgreSQL version (in our case 15.1 ).
818
818
819
819
# ### TLS certificate authentication
820
820
@@ -829,7 +829,7 @@ in the same Kubernetes cluster.
829
829
This example can be easily adapted to cover an instance that resides
830
830
outside the Kubernetes cluster.
831
831
832
- The manifest defines a new PostgreSQL 15.0 cluster called `cluster-clone-tls`,
832
+ The manifest defines a new PostgreSQL 15.1 cluster called `cluster-clone-tls`,
833
833
which is bootstrapped using the `pg_basebackup` method from the `cluster-example`
834
834
external cluster. The host is identified by the read/write service
835
835
in the same cluster, while the `streaming_replica` user is authenticated
@@ -844,7 +844,7 @@ metadata:
844
844
name: cluster-clone-tls
845
845
spec:
846
846
instances: 3
847
- imageName: ghcr.io/cloudnative-pg/postgresql:15.0
847
+ imageName: ghcr.io/cloudnative-pg/postgresql:15.1
848
848
849
849
bootstrap:
850
850
pg_basebackup:
0 commit comments