+++ This bug was initially created as a clone of Bug #1817250 +++ Description of problem: Migrations of applications on source clusters that use API versions which have been removed from the target cluster will not work in CAM 1.1.2. This will pose a problem for migrating from OCP 3.7 to OCP 4.4, common resources such as Deployments will not migrate. For example, If a source cluster has an application using 'apps.v1beta1.Deployment' that resource will not be able to be migrated to a target that is only serving 'apps.v1.Deployment'. OCP 4.3 was serving both 'apps.v1beta1.Deployment' and 'apps.v1.Deployment', in OCP 4.4 the 'apps.v1beta1.Deployment' was dropped. OCP 4.4 only has 'apps.v1.Deployment', so applications using the older version will not migrate over. Below blog post describes some of the APIs which were removed in k8s 1.16, these were still enabled in OCP 4.3, but have since been removed in OCP 4.4. https://kubernetes.io/blog/2019/07/18/api-deprecations-in-1-16/ CAM 1.2.0 has work to validate the required api versions and warn when an issue is seen. This is not present in CAM 1.1.2.
verified
Changes merged. Updated doc will appear with 4.4 release.