Description of problem: Network Operator CRD in openshift/api is not copied to release payload. But instead another CRD present in cluster-network-operator repo is copied. This is causing a mismatch in CRD spec. For example, log level validation in CRD spec is not seen in a 4.7 cluster. > $ oc get crd networks.operator.openshift.io -o jsonpath="{.spec.versions[0].schema.openAPIV3Schema.properties.spec.properties.logLevel}" > map[description:logLevel allows configuring the logging level of the components deployed by the operator. Currently only Kuryr SDN is affected by this setting. Please note that turning on extensive logging may affect performance. The default value is "Normal". type:string] https://github.com/openshift/api/blob/master/operator/v1/0000_70_cluster-network-operator_01_crd.yaml#L372-L386 As I understand, this file is copied to the cluster. https://github.com/openshift/cluster-network-operator/blob/master/manifests/0000_70_cluster-network-operator_01_crd.yaml
Background: openshift/api is the source of thruth for our API definitions. Every operator is supposed to copy from there into their manifests/ directory DURING image builds.
will look into this today
https://github.com/openshift/cluster-network-operator/pull/863 should have fixed this.