mirror of
https://github.com/openshift/openshift-docs.git
synced 2026-02-05 12:46:18 +01:00
Customer update backup repository password
This commit is contained in:
committed by
openshift-cherrypick-robot
parent
12dfc2f9c0
commit
da8b8423be
@@ -32,6 +32,15 @@ endif::[]
|
||||
====
|
||||
If you do not want to specify backup or snapshot locations during the installation, you can create a default `Secret` with an empty `credentials-velero` file. If there is no default `Secret`, the installation will fail.
|
||||
====
|
||||
+
|
||||
[NOTE]
|
||||
====
|
||||
Velero creates a secret named `velero-repo-credentials` in the OADP namespace, which contains a default backup repository password.
|
||||
You can update the secret with your own password encoded as base64 *before* you run your first backup targeted to the backup repository. The value of the key to update is `Data[repository-password]`.
|
||||
|
||||
After you create your DPA, the first time that you run a backup targeted to the backup repository, Velero creates a backup repository whose secret is `velero-repo-credentials`, which contains either the default password or the one you replaced it with.
|
||||
If you update the secret password *after* the first backup, the new password will not match the password in `velero-repo-credentials`, and therefore, Velero will not be able to connect with the older backups.
|
||||
====
|
||||
|
||||
.Procedure
|
||||
|
||||
|
||||
Reference in New Issue
Block a user