From d0422d8ee5a6022b6750c84aca3283a82ac437c2 Mon Sep 17 00:00:00 2001 From: Tiger Kaovilai Date: Tue, 8 Mar 2022 10:39:01 -0500 Subject: [PATCH] Clarify backups that get deleted via object storage sync Signed-off-by: Tiger Kaovilai --- site/content/docs/main/how-velero-works.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/site/content/docs/main/how-velero-works.md b/site/content/docs/main/how-velero-works.md index 250ab2dab..cd227b22a 100644 --- a/site/content/docs/main/how-velero-works.md +++ b/site/content/docs/main/how-velero-works.md @@ -77,7 +77,8 @@ Velero treats object storage as the source of truth. It continuously checks to s This allows restore functionality to work in a cluster migration scenario, where the original backup objects do not exist in the new cluster. -Likewise, if a backup object exists in Kubernetes but not in object storage, it will be deleted from Kubernetes since the backup tarball no longer exists. +Likewise, if a `Completed` backup object exists in Kubernetes but not in object storage, it will be deleted from Kubernetes since the backup tarball no longer exists. +`Failed` or `PartiallyFailed` backup will not be removed by object storage sync. [10]: backup-hooks.md [11]: restore-hooks.md