vmware-tanzu
/
velero
mirror of https://github.com/vmware-tanzu/velero.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

A little note about TTL expiration 

I think is necessary this little comment about TTL expiration, because it can be confusing when the expiration time has passed and the data allocated and the snapshots are not erased at that time.

Signed-off-by: Aaron Arias <33655005+aaronariasperez@users.noreply.github.com>
pull/5315/head
Aaron Arias 2022-09-08 12:40:51 +02:00 committed by GitHub
parent 8888f8765e
commit 901bec30dd
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 2 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
site/content/docs/v1.9/how-velero-works.md
View File

@ -88,6 +88,8 @@ When you create a backup, you can specify a TTL (time to live) by adding the fla
The TTL flag allows the user to specify the backup retention period with the value specified in hours, minutes and seconds in the form `--ttl 24h0m0s`. If not specified, a default TTL value of 30 days will be applied.
The effects of expiration are not applied immediately, they are applied when the gc-controller runs its reconciliation loop every hour.
If backup fails to delete, a label `velero.io/gc-failure=<Reason>` will be added to the backup custom resource.
You can use this label to filter and select backups that failed to delete.