From 9320836b4fcc206d0ef43e803b924218ce34553b Mon Sep 17 00:00:00 2001 From: Itay Grudev Date: Sun, 8 Oct 2023 03:12:15 +0300 Subject: [PATCH] Fixed typo in the recovery documentation Signed-off-by: Itay Grudev --- charts/cluster/docs/Recovery.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/charts/cluster/docs/Recovery.md b/charts/cluster/docs/Recovery.md index 55ea262f7..6a1be6593 100644 --- a/charts/cluster/docs/Recovery.md +++ b/charts/cluster/docs/Recovery.md @@ -1,16 +1,16 @@ Recovery ======== -This chart can be used to initiate a recovery opetation of a CNPG cluster no matter if it was created with the chart or not. +This chart can be used to initiate a recovery operation of a CNPG cluster no matter if it was created with the chart or not. -CNPG does not support recovery in-place. Instead you need to create a new cluster that will be bootstrapped from the existing one or a backup. +CNPG does not support recovery in-place. Instead you need to create a new cluster that will be bootstrapped from the existing one or from a backup. You can find more information about the recovery process in the [CNPG documentation](https://cloudnative-pg.io/documentation/current/backup_recovery). There are 3 types of recovery possible with CNPG: * Recovery from a backup object in the same Kubernetes namespace. * Recovery from a Barman Object Store, that could be located anywhere. -* Streaming replication from an operating cluster using `pg_basebackup` (not supported by the chart). +* Streaming replication from an operating cluster using `pg_basebackup` (not supported by the chart yet). When performing a recovery you are strongly advised to use the same configuration and PostgreSQL version as the original cluster.