Fix the velero crd define locations. (#6554)

Signed-off-by: yanggang <gang.yang@daocloud.io>
This commit is contained in:
Yang Gang
2023-07-31 15:58:07 +08:00
committed by GitHub
parent 3e631ca466
commit 16613f5fe1
2 changed files with 2 additions and 2 deletions

View File

@@ -89,7 +89,7 @@ will be deleted and at that point any uploads still in progress should be aborte
### Uploading (new) ### Uploading (new)
The "Uploading" phase signifies that the main part of the backup, including snapshotting has completed successfully The "Uploading" phase signifies that the main part of the backup, including snapshotting has completed successfully
and and uploading is continuing. In the event of an error during uploading, the phase will change to and uploading is continuing. In the event of an error during uploading, the phase will change to
UploadingPartialFailure. On success, the phase changes to Completed. The backup cannot be UploadingPartialFailure. On success, the phase changes to Completed. The backup cannot be
restored from when it is in the Uploading state. restored from when it is in the Uploading state.

View File

@@ -503,7 +503,7 @@ func (s *server) veleroResourcesExist() error {
} }
if len(errs) > 0 { if len(errs) > 0 {
errs = append(errs, errors.New("Velero custom resources not found - apply examples/common/00-prereqs.yaml to update the custom resource definitions")) errs = append(errs, errors.New("Velero custom resources not found - apply config/crd/v1/bases/*.yaml,config/crd/v2alpha1/bases*.yaml, to update the custom resource definitions"))
return kubeerrs.NewAggregate(errs) return kubeerrs.NewAggregate(errs)
} }