Bug 1885250 - prom-label-proxy: Logging is broken due to mix of k8s.io/klog v1 and v2
Summary: prom-label-proxy: Logging is broken due to mix of k8s.io/klog v1 and v2
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Monitoring
Version: 4.6
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: 4.7.0
Assignee: Sergiusz Urbaniak
QA Contact: Junqi Zhao
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-10-05 13:47 UTC by Sergiusz Urbaniak
Modified: 2020-10-13 07:54 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-10-13 07:54:31 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Sergiusz Urbaniak 2020-10-05 13:47:03 UTC 
This bug was initially created as a copy of Bug #1883461

I am copying this bug because: 



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).
Comment 1 Simon Pasquier 2020-10-13 07:54:31 UTC 
prom-label-proxy doesn't use klog either directly or indirectly.
Note You need to log in before you can comment on or make changes to this bug.