Description of problem: Description is empty when oc explain authentication.operator.openshift.io Version-Release number of selected component (if applicable): 4.3.0-0.nightly-2019-11-06-215135 How reproducible: Always Steps to Reproduce: #### v4.3 $ oc explain authentication --api-version='operator.openshift.io/v1' KIND: Authentication VERSION: operator.openshift.io/v1 DESCRIPTION: <empty>
One minor issue: It is empty for spec and status field for authentication.operator.openshift.io, while it is not for authentication.config.openshift.io. Will any further modification be done? Thanks. $ oc explain authentication --api-version='operator.openshift.io/v1' KIND: Authentication VERSION: operator.openshift.io/v1 DESCRIPTION: Authentication provides information to configure an operator to manage authentication. 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> $ oc explain authentication KIND: Authentication VERSION: config.openshift.io/v1 DESCRIPTION: Authentication specifies cluster-wide settings for authentication (like OAuth and webhook token authenticators). The canonical name of an instance is `cluster`. 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- spec holds user settable values for configuration status <Object> status holds observed values from the cluster. They may not be overridden.
That description being empty is ok for now
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