Description of problem: Kubernetes API version for CustomResourceDefinition is now v1. So, Forklift/MTV should use this API version when declaring its CRDs. MTV 2.0.0 is our first stable version. MTV API version should be v1beta1.
From a QE point of view, it means that the API calls to create the MTV CRs should reference forklift.konveyor.io/v1beta1 API version.
https://github.com/konveyor/forklift-controller/pull/206
(In reply to Fabien Dupont from comment #1) > From a QE point of view, it means that the API calls to create the MTV CRs > should reference forklift.konveyor.io/v1beta1 API version. Ok, so that's incorrect, since this PR only changes the CRD definition. The test for this BZ is only regression test.
The fix should be part of build 2.0.0-17 / iib:66911.
@fdupont I am not sure what to test here in 2.0.0-20: "...no matches for kind "Plan" in version "forklift.konveyor.io/v1beta1" are we missing something?
Yes, I wrote in comment #3 that this should only be regression tests.
Tested the move to apiVersion v1beta1 on mtv-operator-bundle-container-2.0.0-4 on MTV installation and in plan/migration CRs
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (MTV 2.0.0 images), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2021:2381