Hide Forgot
Description of problem: Kube-apiserver is patched with the below command to set the log level as 'Normal', but still the kube-apiserver logs shows TRACE level messages. #oc patch kubeapiserver.operator/cluster --type=json -p '[{"op": "replace", "path": "/spec/logLevel", "value": "Normal" }]' Version-Release number of selected component (if applicable): 4.4 How reproducible: Always Steps to Reproduce: 1.Patch the kube-apiserver. #oc patch kubeapiserver.operator/cluster --type=json -p '[{"op": "replace", "path": "/spec/logLevel", "value": "Normal" }]' 2.Check the logs once the kube-apiserver pod rolled out. 3.It shows some TRACE level messages. Actual results: Showing Trace level messages, which consumes more space for logging trace level messages Expected results: Should not show the Trace level messages Additional info:
I am not able to reproduce this in a 4.4 cluster. "TRACE" in the log message here should not be confused with log levels. These messages are dumped by utility named tracer inside kube-apiserver. "Normal", "Debug", "Trace", "TraceAll" have verbosity levels of 2, 4, 6, 8. Verbosity level kube-apiserver is using can be confirmed from the command line options printed to the log output.