You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After upgrading KEDA to version 2.15.1 , the operator-metrics-apiserver is displaying unexpected logging behavior, including excessive log output at ERROR level.
Expected Behavior
The operator-metrics-apiserver should log only at the ERROR level by default.
The allowed values for the stderrthreshold configuration are: 'DEBUG','INFO','WARN','ERROR','ALERT','EMERG'
Actual Behavior
The operator-metrics-apiserver outputs logs of all levels by default.
The operator crashes when attempting to set the stderrthreshold to any value other than ERROR .
Steps to Reproduce the Problem
Upgrade KEDA to version 2.15.1 .
Observe the logs of operator-metrics-apiserver.
Change the stderrthreshold to any value other than ERROR
Thank you for looking into this! Just to clarify, would the PR need to update k8s.io/klog/v2 from version v2.120.1 to v2.130.1 to pull in the fix for the stderrthreshold issue?
After upgrading KEDA to version 2.15.1 , the operator-metrics-apiserver is displaying unexpected logging behavior, including excessive log output at ERROR level.
Expected Behavior
The operator-metrics-apiserver should log only at the ERROR level by default.
The allowed values for the
stderrthreshold
configuration are: 'DEBUG','INFO','WARN','ERROR','ALERT','EMERG'Actual Behavior
The operator-metrics-apiserver outputs logs of all levels by default.
The operator crashes when attempting to set the stderrthreshold to any value other than ERROR .
Steps to Reproduce the Problem
operator-metrics-apiserver
.stderrthreshold
to any value other than ERRORSpecifications
Attached files
crash.txt
censored logs with traces.txt
kedacore/keda#5139
The text was updated successfully, but these errors were encountered: