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 1769621 has been marked as a duplicate of this bug. ***
API changes landed in 4.3, but client-go has not landed yet.
@Ricardo at this point it may be easier to keep the existing client in the image registry operator repo, and merely regenerate it by bumping openshift/api. Keep in mind that we will want to backport this change to the release-4.3 branch.
[wzheng@openshift-qe 4.4]$ ./oc version
Client Version: v4.4.0
Server Version: 4.4.0-0.nightly-2019-12-15-184910
Kubernetes Version: v1.16.2
[wzheng@openshift-qe 4.4]$ ./oc explain configs --api-version=imageregistry.operator.openshift.io/v1
[wzheng@openshift-qe 4.4]$ ./oc get clusterversion
NAME VERSION AVAILABLE PROGRESSING SINCE STATUS
version 4.4.0-0.nightly-2019-12-15-184910 True False 6h55m Cluster version is 4.4.0-0.nightly-2019-12-15-184910
I still cannot see the fix, so assign back.
Test with 4.4.0-0.nightly-2019-12-20-210709 payload, and pass
Client Version: v4.3.0
Server Version: 4.4.0-0.nightly-2019-12-20-210709
Kubernetes Version: v1.17.0
$oc explain configs --api-version=imageregistry.operator.openshift.io/v1
Config is the configuration object for a registry instance managed by the
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:
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:
metadata <Object> -required-
Standard object's metadata. More info:
spec <Object> -required-
ImageRegistrySpec defines the specs for the running registry.
ImageRegistryStatus reports image registry operational status.
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.