*** Bug 1803091 has been marked as a duplicate of this bug. ***
PR is ready and soon merging.
Verified with following ENV, # oc version oc v3.11.217 kubernetes v1.11.0+d4cacc0 features: Basic-Auth GSSAPI Kerberos SPNEGO Server https://ip-...-..-..-....ec2.internal:8443 openshift v3.11.219 kubernetes v1.11.0+d4cacc0 Open the prometheus web console, searching the following metrics, apiserver_request_count{code="200",contentType="application/json",endpoint="https",instance="1...:8443",job="apiserver",namespace="default",resource="alertmanagers",scope="cluster",service="kubernetes",verb="LIST"} apiserver_request_latencies_bucket{endpoint="https",instance="1...:8443",job="apiserver",le="+Inf",namespace="default",resource="alertmanagers",scope="cluster",service="kubernetes",verb="LIST"} apiserver_request_latencies_count{endpoint="https",instance="1...:8443",job="apiserver",namespace="default",resource="alertmanagers",scope="cluster",service="kubernetes",verb="LIST"} apiserver_request_latencies_sum{endpoint="https",instance="1...:8443",job="apiserver",namespace="default",resource="alertmanagers",scope="cluster",service="kubernetes",verb="LIST"} apiserver_request_latencies_summary{endpoint="https",instance="1...:8443",job="apiserver",namespace="default",quantile="0.5",resource="alertmanagers",scope="cluster",service="kubernetes",verb="LIST"} apiserver_request_latencies_summary_count{endpoint="https",instance="1...:8443",job="apiserver",namespace="default",resource="alertmanagers",scope="cluster",service="kubernetes",verb="LIST"} apiserver_request_latencies_summary_sum{endpoint="https",instance="1...:8443",job="apiserver",namespace="default",resource="alertmanagers",scope="cluster",service="kubernetes",verb="WATCH"} From above we can see apiserver_request_count and apiserver_request_latencies at the prometheus related metrics, the label ‘client’ was gone, it is as expected.
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-2020:2215
*** Bug 1798289 has been marked as a duplicate of this bug. ***