@@ -468,7 +468,7 @@ file on the source PostgreSQL instance:
468
468
host replication streaming_replica all md5
469
469
` ` `
470
470
471
- The following manifest creates a new PostgreSQL 15.3 cluster,
471
+ The following manifest creates a new PostgreSQL 15.4 cluster,
472
472
called `target-db`, using the `pg_basebackup` bootstrap method
473
473
to clone an external PostgreSQL cluster defined as `source-db`
474
474
(in the `externalClusters` array). As you can see, the `source-db`
@@ -483,7 +483,7 @@ metadata:
483
483
name: target-db
484
484
spec:
485
485
instances: 3
486
- imageName: ghcr.io/cloudnative-pg/postgresql:15.3
486
+ imageName: ghcr.io/cloudnative-pg/postgresql:15.4
487
487
488
488
bootstrap:
489
489
pg_basebackup:
@@ -503,7 +503,7 @@ spec:
503
503
` ` `
504
504
505
505
All the requirements must be met for the clone operation to work, including
506
- the same PostgreSQL version (in our case 15.3 ).
506
+ the same PostgreSQL version (in our case 15.4 ).
507
507
508
508
# ### TLS certificate authentication
509
509
@@ -518,7 +518,7 @@ in the same Kubernetes cluster.
518
518
This example can be easily adapted to cover an instance that resides
519
519
outside the Kubernetes cluster.
520
520
521
- The manifest defines a new PostgreSQL 15.3 cluster called `cluster-clone-tls`,
521
+ The manifest defines a new PostgreSQL 15.4 cluster called `cluster-clone-tls`,
522
522
which is bootstrapped using the `pg_basebackup` method from the `cluster-example`
523
523
external cluster. The host is identified by the read/write service
524
524
in the same cluster, while the `streaming_replica` user is authenticated
@@ -533,7 +533,7 @@ metadata:
533
533
name: cluster-clone-tls
534
534
spec:
535
535
instances: 3
536
- imageName: ghcr.io/cloudnative-pg/postgresql:15.3
536
+ imageName: ghcr.io/cloudnative-pg/postgresql:15.4
537
537
538
538
bootstrap:
539
539
pg_basebackup:
0 commit comments