Created attachment 1592686 [details] Descriptions in console The various cluster config config.openshift.io resource descriptions have been copied and pasted from each other and have no detail. Administrators don't know what these configurations are for. I've attached a screenshot of how this looks in console (not good) and why we want to update each description. Per Clayton, this is a high severity bug.
The Image Registry / Image Registry Operator does not show up on this global configuration list. Was this bug created erroneously? If this bug is valid, can you please give some further guidance on exactly what you would like done
Does this comment help https://bugzilla.redhat.com/show_bug.cgi?id=1732145#c8 ?
Yes, thank you!
The bug fixed in 4.2.0-0.nightly-2019-09-16-175247 payload. $oc explain image --api-version=config.openshift.io/v1 KIND: Image VERSION: config.openshift.io/v1 DESCRIPTION: Image governs policies related to imagestream imports and runtime configuration for external registries. It allows cluster admins to configure which registries OpenShift is allowed to import images from, extra CA trust bundles for external registries, and policies to blacklist/whitelist registry hostnames. When exposing OpenShift's image registry to the public, this also lets cluster admins specify the external hostname. 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. And the image.config.openshift.io crd has updated too.
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
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days