Description of problem:
Deleting a Plan (ui+API) doesn't remove the migration importer & migration PODS
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.Run A successful migration and delete it
cdi-import and the conversion pods are not removed.
cdi-import and the conversion pods should be removed.
After talking this over with Jeff, it's clear to me that we can't proceed with the finalizer-based solution I proposed. Jeff mentioned that MTC had the same problem they attempted a finalizer-based solution as well, but finalizers are inherently fraught with issues (race conditions preventing resources from being deleted, etc), and that approach was abandoned. Unfortunately, there's no alternative that would let us archive the plan upon deletion. We should document that the user must archive the plan before deleting it if they want the plan's resources to be removed, and perhaps we could have the UI warn before allowing an unarchived Plan to be deleted.
Removed the Blocker bug for MTV-2.2.
Bug 2022651 - [UI] Add the Delete migration plan message that the related resources will remain
Bug 2022654 - [Doc] cdi-Importer & migration pods and all related resources are not removed when the Plan is Removed
When this bug is implemented the Delete Migration plan message in Bug 2022651 will need to change to reflect that deleting the migration plan will delete related resources.