oc explain configs.spec --api-version=imageregistry.operator.openshift.io/v1
logging <integer> -required-
logging determines the level of logging enabled in the registry.
Should actually tell me what 0, 1, 2, 3, 4 mean. Otherwise I can't (in console or CLI) actually determine what to set. We should describe the int, the level, and what output it includes.
This is an important field, this is a common debug operation, so setting to high.
Note, in 4.6 it's going to be deprecated by logLevel, but it's important to update docs in older releases.
Note 2: CRD comes via the image registry operator, so docs needs to be updated, and the update needs to be vendored to cluster-image-registry-operator.
This field is being deprecated on 4.6. There is not much we can do here other than wait until the changes land on https://bugzilla.redhat.com/show_bug.cgi?id=1808118.
Still awaiting for https://bugzilla.redhat.com/show_bug.cgi?id=1808118
Fixed by https://github.com/openshift/api/pull/640.
logLevel is an intent based logging for an overall component. It does not
give fine grained control, but it is a simple way to manage coarse grained
logging choices that operators have to interpret for their operands. Valid
values are: "Normal", "Debug", "Trace", "TraceAll". Defaults to "Normal".
Verified on 4.6.0-0.nightly-2020-09-10-195619.
logging is deprecated, use logLevel instead.
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 (OpenShift Container Platform 4.6 GA Images), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.