Details
-
Risk
-
Resolution: Done
-
Major
-
fuse-7.9-GA
-
None
-
False
-
False
-
GA
-
%
-
Verified on all OCP 3.11 and it is working without issue.
-
High
-
0
-
Scope
-
Highly Likely
-
Reduction or control
Description
After replacement CRD api version to v1 (original Enhancement https://issues.redhat.com/browse/ENTESB-15801), we will lost a support for OCP 3.11 since 3.11 uses kubernetes Version: v1.11.0 (apiextensions.k8s.io/v1 is since v1.16).
After that, creation of CRD in 3.11 would fail (error: unable to recognize "": no matches for kind "CustomResourceDefinition" in version "apiextensions.k8s.io/v1").
If we want to support 3.11 after that change, we need to have two CRD for both platforms (OCP4 and OCP3) and they need to be distinguish (somehow) during the installation.