What to do with owned resources during cluster migration?

[irbekrm]

At the moment jsctl x clusters backup command cleans up most fields that could cause issues during restore such as UUID.

It does not however clean up owner references on resources.

I am not sure in what cases users would be migrating owned resources (issuers etc). I assume that if resources were owned (i.e by another controller) the migration would require extra custom steps.

There's a couple extra steps we could do:

• jsctl x clusters uninstall verify command could print a warning if owner references found either on custom resources or CSI driver etc deployments
• jsctl clusters status command could output how a resource/compoent installation was deployed (on basis of helm, kubectl annotations, owner refs etc)
• jsctl x clusters backup command could optionally clean up owner references

Perhaps we could wait to see if any such scenario comes up to determine what would be the best action to take.