Scott Seago

Now that the overall design changes have been approved, this PR is ready for review.

The issue is that Velero doesn't know it didn't create it, since the normal install procedure is to create the namespace and then create the velero resources. As mentioned above,...

With this feature, we're moving away from the idea of creating separate pods for concurrent backups (either with or without Jobs), mentioned in previous design PRs linked here, for a...

> @kaovilai Thanks for following up on this PR. For this iteration, is it possible to release artifacts similar to [this](https://github.com/vmware-tanzu/velero/pull/1605) `ppc64le` implementation? I am unable to determine `ppc64le` CI...

Now that csi plugin functionality has been moved to vmware-tanzu/velero main, we shouldn't be merging any more PRs to main here. If something is needed on a release branch, then...

Supporting the registry here was one of the reasons we added the prefix in the first place -- the registry can't be in the same prefix as the velero backup,...

> > Supporting the registry here was one of the reasons we added the prefix in the first place > > You mean adding the prefix to `BackupStorageLocation.spec.objectStorage.prefix`, correct? >...

> > so maybe this data should actually go to /plugins/openshift-velero-plugin/docker/registry/...: > > Sure. But it would be a breaking change. or require some migration effort. And actually, any change...