Migration permutations and deprecations: when migrating from some legacy product (eg VM deployments) to some newer product (eg k8s) there is an explicit fork of the platform's stack, which we notice forces us to support lots of edge cases that only exist in the migration limbo (eg discovering and access controlling services across VMs and k8s), and whihc in turn create barriers for migration.
How do folks here choose which limbo edge cases to support?
Or, how do you plan your migrations such that you minimize these limbo barriers or avoid them entirely? (Eg don't do MVPs and iterate and just build a complete replacement of the existing solution?)
Lastly, what do you do when you are doing several of these stack migrations at once? Or do you explicitly limit yourselves to one platform fork at a time?