From 901bec30ddc03e21898bc256a542083635ab47c8 Mon Sep 17 00:00:00 2001 From: Aaron Arias <33655005+aaronariasperez@users.noreply.github.com> Date: Thu, 8 Sep 2022 12:40:51 +0200 Subject: [PATCH] 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> --- site/content/docs/v1.9/how-velero-works.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/site/content/docs/v1.9/how-velero-works.md b/site/content/docs/v1.9/how-velero-works.md index 19fc89a94..227c927c1 100644 --- a/site/content/docs/v1.9/how-velero-works.md +++ b/site/content/docs/v1.9/how-velero-works.md @@ -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=` will be added to the backup custom resource. You can use this label to filter and select backups that failed to delete.