+++ This bug was initially created as a clone of Bug #1781768 +++ Seeing E1209 06:35:01.956334 1 customresource_handler.go:655] error building openapi models for clusteroperators.config.openshift.io: ERROR $root.definitions.io.openshift.config.v1.ClusterOperator.properties.status.properties.extension has invalid property: nullable in kube-apiserver logs from https://storage.googleapis.com/origin-ci-test/logs/release-openshift-ocp-installer-e2e-aws-4.3/453/artifacts/e2e-aws/pods/openshift-kube-apiserver_kube-apiserver-ip-10-0-143-43.ec2.internal_kube-apiserver-3.log in https://prow.svc.ci.openshift.org/view/gcs/origin-ci-test/logs/release-openshift-ocp-installer-e2e-aws-4.3/453 . I think this impacts explain output and may indicate that we have different definitions of the clusteroperator CRD fighting.
Verified in 4.3.0-0.nightly-2019-12-24-014531: oc get crd -o yaml | grep nullable Given CRDs have nullable property, KAS pod logs don't have above errors now. Per the upstream k8s issue https://github.com/kubernetes/kubernetes/issues/85127 , everything kept working, thus lowering severity. Reporting a separate bug 1786273 for another similar error.
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, 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/RHBA-2020:0062