From d714c3c237280463fd0cedf8cfbc9595d2859082 Mon Sep 17 00:00:00 2001 From: Tiger Kaovilai Date: Wed, 6 Sep 2023 16:32:36 -0400 Subject: [PATCH] Show yaml example of repository password: file-system-backup.md Signed-off-by: Tiger Kaovilai --- site/content/docs/main/file-system-backup.md | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/site/content/docs/main/file-system-backup.md b/site/content/docs/main/file-system-backup.md index 178d9c0f30..3680498869 100644 --- a/site/content/docs/main/file-system-backup.md +++ b/site/content/docs/main/file-system-backup.md @@ -65,7 +65,11 @@ There may be additional installation steps depending on the cloud provider plugi [plugin specific documentation](supported-providers.md) for the must up to date information. **Note:** Currently, Velero creates a secret named `velero-repo-credentials` in the velero install namespace, containing a default backup repository password. -You can update the secret with your own password encoded as base64 prior to the first backup (i.e., FS Backup, data mover) targeting to the backup repository. The value of the key to update is `Data[repository-password]`. +You can update the secret with your own password encoded as base64 prior to the first backup (i.e., FS Backup, data mover) targeting to the backup repository. The value of the key to update is +``` +data: + repository-password: +``` Backup repository is created during the first execution of backup targeting to it after installing Velero with node agent. If you update the secret password after the first backup which created the backup repository, then Velero will not be able to connect with the older backups.