Goal

Keep all the assets related to a migration plan even if it runs more than once

Background

Running a migration plan will generate several tokens of data like Custom Resources and Logs from pods. 

When running a migration plan for the second time it shall not overwrite previous content but add to them or generate new instances.

At some point in time we may want to add the capability to review and delete the content related to each run of a plan.

User Stories

As a migration user, I want to keep the migration assets until I decide to delete them, so that I will be able to review and troubleshoot a migration.

Implementation Notes

The implementation will create a new state for the Plan CR named Archived. When the Plan is in Complete state, the various assets should be kept: managed CR and pods, so that the logs can be retrieved afterwards (see MTV-31).

Possibly, the easiest way to implement the retention is to set the OwnerReference on the generated resources, so that the garbage collector doesn't delete them.