Bug 1831711

+++ This bug was initially created as a clone of Bug #1831705 +++

Description of problem:
When we create resources using apps/v1 endpoint in ocp4.2 and we want to migrate them to ocp4.4, the migration shows a warning saying that those resources cannot be migrated because they are incompatible with ocp4.4 because they use extensions/v1beta1  and apps/v1beta2 endpoints.

Version-Release number of selected component (if applicable):
SOURCE CLUSTER: 4.2
TARGET CLUSTER: 4.4
KONVEYOR 1.2

How reproducible:
Always

Steps to Reproduce:
1. In source cluster create a deployment using apps/v1 endpoint. For instance:

oc new-project hello-openshift

cat <<EOF | oc create -f -
apiVersion: apps/v1
kind: Deployment
metadata:
  name: hello-openshift
spec:
  replicas: 1
  selector:
    matchLabels:
      app: hello-openshift
  template:
    metadata:
      labels:
        app: hello-openshift
    spec:
      containers:
      - name: hello-openshift
        image: openshift/hello-openshift:latest
        ports:
        - containerPort: 80
EOF

2. Create a migration plan to migrate this namespace

Actual results:
The migration plan says that there are resources in this namespaces that cannot be migrated because they use extensions/v1beta1  and apps/v1beta2 endpoints. Nevertheless, the resource that we have created actually uses apps/v1 endpoint.

  status:
    conditions:
    - category: Warn
      lastTransitionTime: "2020-05-05T08:39:15Z"
      message: 'Some namespaces contain GVKs incompatible with destination cluster.
        See: `incompatibleNamespaces` for details'
      status: "True"
      type: GVKsIncompatible
    - category: Required
      lastTransitionTime: "2020-05-05T08:39:16Z"
      message: The `persistentVolumes` list has been updated with discovered PVs.
      reason: Done
      status: "True"
      type: PvsDiscovered
    - category: Required
      lastTransitionTime: "2020-05-05T08:39:18Z"
      message: The storage resources have been created.
      status: "True"
      type: StorageEnsured
    - category: Required
      lastTransitionTime: "2020-05-05T08:39:20Z"
      message: The migration registry resources have been created.
      status: "True"
      type: RegistriesEnsured
    - category: Required
      lastTransitionTime: "2020-05-05T08:39:20Z"
      message: The migration plan is ready.
      status: "True"
      type: Ready
    incompatibleNamespaces:
    - gvks:
      - group: extensions
        kind: deployments
        version: v1beta1
      - group: extensions
        kind: replicasets
        version: v1beta1
      - group: apps
        kind: deployments
        version: v1beta2
      - group: apps
        kind: replicasets
        version: v1beta2
      - group: apps
        kind: deployments
        version: v1beta1
      name: hello-openshift


Expected results:
The namespace and its resources should be migrated without problems.

Additional info:

when I get the resource, it's true that by default it's shown as v1beta1. But it actually is a v1 deployment

$ oc get deployments -o yaml | grep "\- apiVer"
- apiVersion: extensions/v1beta1
$ oc get deployments.apps -o yaml | grep "\- apiVer"
- apiVersion: apps/v1

This issue may explain what happens in the cluster
https://github.com/kubernetes/kubernetes/issues/58131