Description of problem: Verbose log is activated on the container "kube-rbac-proxy" in the deployment "prometheus-k8s" in Cluster Monitoring Operator. Too many logs are generated for production environment, adding system load factor without useful benefits. We are going to remove it. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Verbose log is on for the container "kube-rbac-proxy" in the deployment "prometheus-k8s" in Cluster Monitoring Operator. Expected results: Verbose log is off for the container "kube-rbac-proxy" in the deployment "prometheus-k8s" in Cluster Monitoring Operator. Additional info:
release: 4.11.0-0.nightly-2022-06-09-202040 test process: % oc logs -n openshift-monitoring -f prometheus-k8s-0 -c kube-rbac-proxy I0610 01:36:56.749971 1 main.go:151] Reading config file: /etc/kube-rbac-proxy/config.yaml I0610 01:36:56.753246 1 main.go:181] Valid token audiences: I0610 01:36:56.753657 1 main.go:305] Reading certificate files I0610 01:36:56.753778 1 dynamic_cafile_content.go:167] Starting client-ca::/etc/tls/client/client-ca.crt I0610 01:36:56.753885 1 main.go:339] Starting TCP socket on 0.0.0.0:9092 I0610 01:36:56.754338 1 main.go:346] Listening securely on 0.0.0.0:9092 The amount of logs is limited, all test passed
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 (Important: OpenShift Container Platform 4.11.0 bug fix and security update), 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/RHSA-2022:5069