The following PR https://github.com/openshift/origin/pull/22696 introduced an e2e which is verifying that all the operators provide descriptive information as part of their schema which is then available through oc explain command. This was recently updated and brought back in https://github.com/openshift/origin/pull/24058. Your component has a few missing bits, see the commented out lines from the PR. This should be fixed similarly to https://github.com/openshift/cluster-kube-controller-manager-operator/pull/302, iow. it should be using openshift/api's generated CRD yamls. Once done update origin's e2e test and uncomment the lines from your components.
*** Bug 1769622 has been marked as a duplicate of this bug. ***
Nihgtly build version are not include the merge, so verified in CI image version: registry.svc.ci.openshift.org/ocp/release:4.3.0-0.ci-2019-11-15-040751 [root@Desktop ~]# /home/wewang/Downloads/oc explain openshiftcontrollermanager KIND: OpenShiftControllerManager VERSION: operator.openshift.io/v1 DESCRIPTION: OpenShiftControllerManager provides information to configure an operator to manage openshift-controller-manager. FIELDS: apiVersion <string> APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources kind <string> Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds metadata <Object> Standard object's metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata spec <Object> -required- status <Object>
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