When preparing a backup repository, Velero tries to connect to it, if fails then create it. The repository status always records the error reported by creation but the real reason maybe caused by the connect operation. This is confuseing and hard to debug Signed-off-by: Wenkai Yin(尹文开) <yinw@vmware.com> |
||
---|---|---|
.. | ||
provider.go | ||
restic.go | ||
unified_repo.go | ||
unified_repo_test.go |