Handle namespace mapping #54
Labels
kind/bug
Categorizes issue or PR as related to a bug.
priority/blocker
Highest priority. Must be actively worked on as someone's top priority right now.
triage/accepted
Indicates an issue or PR is ready to be actively worked on.
One feature that we have in the prior generation of Crane/MTC tools is the ability to migrate a workload to a different namespace on the destination cluster. We need something similar in the new crane workflow. There are a few things that we do in MTC via velero and plugins that we'd need to do here as well. This could all be done relatively easily as a crane plugin. It may be possible to do it via something like kustomize as well, but it would probably be more challenging to do it there, so for the moment I'd recommend a plugin for this.
Here are the things that we're currently dealing with that we also need this plugin (or other implementation) to handle:
Here are some cases which we have in velero plugins that deal with namespace swaps that we probably don't need here:
registry-replacement
arg in the kubernetes plugin.The text was updated successfully, but these errors were encountered: