From e9a19581bf034b3b76b61c0b46ec99030bb6762f Mon Sep 17 00:00:00 2001 From: Ashish Amarnath Date: Mon, 2 Nov 2020 11:38:00 -0800 Subject: [PATCH] =?UTF-8?q?=F0=9F=93=96=20Clarify=20restore=20hook=20init?= =?UTF-8?q?=20container=20priority=20(#3030)?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Signed-off-by: Ashish Amarnath --- site/content/docs/main/restore-hooks.md | 4 ++++ site/content/docs/v1.5/restore-hooks.md | 4 ++++ 2 files changed, 8 insertions(+) diff --git a/site/content/docs/main/restore-hooks.md b/site/content/docs/main/restore-hooks.md index 48eb8c1d6..0ec36c5d7 100644 --- a/site/content/docs/main/restore-hooks.md +++ b/site/content/docs/main/restore-hooks.md @@ -11,6 +11,10 @@ Velero supports Restore Hooks, custom actions that can be executed during or aft ## InitContainer Restore Hooks Use an `InitContainer` hook to add init containers into a pod before it's restored. You can use these init containers to run any setup needed for the pod to resume running from its backed-up state. +The InitContainer added by the restore hook will be the first init container in the `podSpec` of the restored pod. +In the case where the pod had volumes backed up using restic, then, the restore hook InitContainer will be added after the `restic-wait` InitContainer. + +NOTE: This ordering can be altered by any mutating webhooks that may be installed in the cluster. There are two ways to specify `InitContainer` restore hooks: 1. Specifying restore hooks in annotations diff --git a/site/content/docs/v1.5/restore-hooks.md b/site/content/docs/v1.5/restore-hooks.md index 48eb8c1d6..0ec36c5d7 100644 --- a/site/content/docs/v1.5/restore-hooks.md +++ b/site/content/docs/v1.5/restore-hooks.md @@ -11,6 +11,10 @@ Velero supports Restore Hooks, custom actions that can be executed during or aft ## InitContainer Restore Hooks Use an `InitContainer` hook to add init containers into a pod before it's restored. You can use these init containers to run any setup needed for the pod to resume running from its backed-up state. +The InitContainer added by the restore hook will be the first init container in the `podSpec` of the restored pod. +In the case where the pod had volumes backed up using restic, then, the restore hook InitContainer will be added after the `restic-wait` InitContainer. + +NOTE: This ordering can be altered by any mutating webhooks that may be installed in the cluster. There are two ways to specify `InitContainer` restore hooks: 1. Specifying restore hooks in annotations