Description of problem: > $ oc explain config.samples.operator.openshift.io > KIND: Config > VERSION: imageregistry.operator.openshift.io/v1 > DESCRIPTION: > <empty> Version-Release number of selected component (if applicable): 4.1.7 How reproducible: 100% Expected results: This should show me the details about what fields we can be put into the config. Additional info:
Sending this over to Image Registry folks since they own the CRD and that's where the information for oc explain come from.
Apparently the proper command is `oc explain --api-version=samples.operator.openshift.io/v1 configs` and we should backport the fix from the bug 1705753 to 4.1.z. The output for the image registry of `oc explain --api-version=imageregistry.operator.openshift.io/v1 configs` is covered by the bug 1714775.
@Eric - to facilitate our 4.1.z update process, it is is required that the bug targeted to 4.1.z has a clone relationship with the 4.2 bug. The bot in fact verifies that the 4.2 bug has been verified before accepting the cherry-pick. Can you close this out and clone https://bugzilla.redhat.com/show_bug.cgi?id=1705753 to 4.1, or do you need me to do it?
*** This bug has been marked as a duplicate of bug 1743376 ***