+++ This bug was initially created as a clone of Bug #1883461 +++ k8s.io/klog moved to v2 in client-go and frieds. The operator does not use v2 yet and hence, we lose one half of the logging output (v2). --- Additional comment from Stefan Schimanski on 2020-09-29 13:09:06 CEST --- I did some tests using openshift-apiserver that uses kube component-base to add klog command line flags: $ ./openshift-apiserver start --config asfd --v=4 I0929 13:04:18.354425 53628 cmd.go:57] v1 klog I0929 13:04:18.354506 53628 cmd.go:58] v2 klog I0929 13:04:18.354512 53628 cmd.go:61] v2 V(2) klog I0929 13:04:18.354515 53628 cmd.go:64] v2 V(4) klog So this means that we DO NOT set verbosity for v1 klog, and hence lose all the klogv1.V(2).Infof output.
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. https://access.redhat.com/errata/RHBA-2020:4196