mirrors/velero
1
0
Fork 0
mirror of https://github.com/vmware-tanzu/velero.git synced 2026-01-08 22:23:15 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

Merge pull request #4729 from kaovilai/doc_failed_orphaned

Browse Source 
Clarify backups that get deleted via object storage sync
This commit is contained in:
Abigail McCarthy
2022-05-16 09:13:46 -04:00
committed by GitHub
parent 15851ac9aa d0422d8ee5
commit 1a325a6706
1 changed files with 2 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

3
site/content/docs/main/how-velero-works.md
View File

@@ -86,7 +86,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