+++ This bug was initially created as a clone of Bug #1708597 +++ Description of problem: Copied from bug 1705746, should add the description info for these CRDs so that `oc explain` can work when try to explain configs.imageregistry.operator.openshift.io crd: $ oc explain configs.imageregistry.operator.openshift.io |grep -i description -A 3 DESCRIPTION: <empty> $ oc explain configs.samples.operator.openshift.io KIND: Config VERSION: imageregistry.operator.openshift.io/v1 DESCRIPTION: <empty> Version-Release number of selected component (if applicable): 4.1.0-0.nightly-2019-05-09-204138 How reproducible: Always Steps to Reproduce: 1.$ oc explain configs.imageregistry.operator.openshift.io 2.$ oc explain configs.samples.operator.openshift.io 3. Actual results: Get nothing about the description. Expected results: Should get the appropriate description. Additional info:
Same to controller-manager $ oc explain openshiftcontrollermanagers KIND: OpenShiftControllerManager VERSION: operator.openshift.io/v1 DESCRIPTION: <empty> 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/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/api-conventions.md#types-kinds metadata <Object> Standard object's metadata. More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#metadata spec <Object> -required- status <Object>
And if use the full name of controllermanager crd. it will return: $ oc explain openshiftcontrollermanagers.operator.openshift.io error: field "operator" does not exist
*** This bug has been marked as a duplicate of bug 1705753 ***