Bug 1683055

https://github.com/openshift/service-ca-operator/pull/35

In the nightly build 4.0.0-0.nightly-2019-03-20-153904, the service-ca-operator still use the payload build in 201903141706, not included this PR.

The issue still not fixed, leave comment in the Jira.

The lack of comments in openshift/api/config/v1/types_cluster_operator.go  and lack of openshift/api/config/v1/types_servica.go results in the lack of description for serviceca clusteroperator.  The description comes directly from comments in the openshift/api/config/v1/types_*.go files.  Checking to see if this is a bug or can close.

Service CA does not have anything to configure, so it needs no top level config (like these do: https://github.com/openshift/api/tree/master/config/v1) Opened this to get the nice descriptions: https://github.com/openshift/api/pull/276

`oc explain` is functional again, but the PR above did not fix.  I've opened this: https://github.com/openshift/api/pull/296 I believe that will finally make the description comments appear.

The PR has been merged since 5 days ago,so move this bug to ON_QA for checking.

Check with build 4.1.0-0.nightly-2019-04-28-064010, the issue still not fixed.

Now that `oc explain` is working and I've checked all other clusteroperators, I see that any CO w/out a corresponding openshift/api/config/v1 type will return similar `oc explain` output:

try:
oc explain servicecatalogcontrollermanager
oc explain servicecatalogapiserver
oc explain openshiftapiserver
oc explain kubecontrollermanager
oc explain kubeapiserver

They all return no descriptions for spec/status, while anything that has a top-level config will return the nice descriptions.
(ingress, dns, authentication) 

Nothing is broken with this, not sure it's a bug, moving to 4.2 for now.

*** This bug has been marked as a duplicate of bug 1712317 ***

This bug should be kept to track the issue instead of closed as DUP per bug 1712317#c16

Please retry, the PR just merged, maybe wasn't in the nightly? Thanks!

I got this from cluster with 'Cluster version is 4.2.0-0.ci-2019-08-01-113614':

$ oc explain serviceca
KIND:     ServiceCA
VERSION:  operator.openshift.io/v1

DESCRIPTION:
     ServiceCA provides information to configure an operator to manage the
     service cert controllers

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-
     spec holds user settable values for configuration

   status	<Object>
     status holds observed values from the cluster. They may not be overridden.

Verified on 4.2.0-0.nightly-2019-08-06-072822

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-2019:2922