[release-1.15] Always create DataUpload configmap in restore namespace #8622
+2
−1
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Thank you for contributing to Velero!
Please add a summary of your change
In the DataUpload RIA, always create the ConfigMap in the Restore (velero) ns rather than the NS that the DataUpload was created in.
In most cases these are the same, but they won't be if the backup was done in a cluster with velero installed in namespace1 and the restore is being done with velero installed in namespace2. In this case, we need the configmap created in the namespace that velero is currently running in.
cherry-pick of #8621
Does your change fix a particular issue?
Fixes #8617
Please indicate you've done the following:
make new-changelog
) or comment/kind changelog-not-required
on this PR.site/content/docs/main
.