From 8f31bff1b53be3056e16da23ecf99cc73f2b68ee Mon Sep 17 00:00:00 2001 From: Abigail McCarthy Date: Fri, 13 May 2022 12:37:58 -0400 Subject: [PATCH] Add note about restoring when resource scaled to 0 Signed-off-by: Abigail McCarthy --- site/content/docs/main/restic.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/site/content/docs/main/restic.md b/site/content/docs/main/restic.md index ac75f0f9d..8fa1dd8b3 100644 --- a/site/content/docs/main/restic.md +++ b/site/content/docs/main/restic.md @@ -248,7 +248,7 @@ Instructions to back up using this approach are as follows: ### Using opt-in pod volume backup -Velero, by default, uses this approach to discover pod volumes that need to be backed up using Restic, where every pod containing a volume to be backed up using Restic must be annotated with the volume's name. +Velero, by default, uses this approach to discover pod volumes that need to be backed up using Restic. Every pod containing a volume to be backed up using Restic must be annotated with the volume's name using the `backup.velero.io/backup-volumes` annotation. Instructions to back up using this approach are as follows: @@ -412,7 +412,7 @@ data: allowPrivilegeEscalation: false readOnlyRootFilesystem: true runAsUser: 1001 - runAsGroup: 999 + runAsGroup: 999 ``` @@ -524,6 +524,8 @@ within each restored volume, under `.velero`, whose name is the UID of the Veler 1. Once all such files are found, the init container's process terminates successfully and the pod moves on to running other init containers/the main containers. +Velero won't restore a resource if a that resource is scaled to 0 and already exists in the cluster. If Velero restored the requested pods in this scenario, the Kubernetes reconciliation loops that manage resources would delete the running pods because its scaled to be 0. Velero will be able to restore once the resources is scaled up, and the pods are created and remain running. + ## 3rd party controllers ### Monitor backup annotation