Repository navigation
stderrthreshold not honored when logtostderr is set #212
Description
Activity
@DirectXMan12 @justinsb @neolit123 @mtaufen could you please take a look?
@pohly @yuzhiquan @munnerz could you please take a look?
Who needs to be tagged to get feedback?
@jayunit100
@hoegaarden
@andyxning
@yagonobre
@vincepri
@detiber
@thockin
@tallclair
@piosz
@brancz
@lavalampEveryone is extremely overloaded. This looks like it may be much more important to you than perhaps to some other people.
The description of the reversion PR is pretty clear about what went wrong. I recommend sending a PR that adds what you need while not triggering the problems mentioned there.
@lavalamp I can understand that you are all loaded with work but this seems a pretty big bug for a logging library and it seems incredible to me that in two years no one has been able to fix it.
@pierluigilenoci please re-read exactly what @lavalamp said. that's what you will hear from any one of us. good luck!
Reacted by Fabio Del VignaIssues go stale after 90d of inactivity.
Mark the issue as fresh with/remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.If this issue is safe to close now please do so with
/close.Send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale/remove-lifecycle stale
@lavalamp @dims any chance to get the PR of @pierluigilenoci approved? Sorry for jumping in, but I am affected by a pod for Azure AKS which is using this library and generating high log storage costs per month ...
Reacted by Pierluigi Lenoci189 remaining items
- added a commit that references this issue
on Jun 22, 2026 - added a commit that references this issue
on Jun 23, 2026 - added a commit that references this issue
on Jun 23, 2026 - added a commit that references this issue
on Jun 25, 2026 - added a commit that references this issue
on Jul 2, 2026 - added 6 commits that reference this issue
on Jul 4, 2026 - added a commit that references this issue
on Jul 13, 2026 - added a commit that references this issue
on Aug 26, 2026 - added a commit that references this issue
on Sep 1, 2026 - added a commit that references this issue
on Oct 6, 2026
/kind bug
What steps did you take and what happened:
[A clear and concise description of what the bug is.]
We're using the
kloglogging framework in Secrets Store CSI Driver. When trying to set-stderrthreshold=ERRORwith-logtostderr=true, we're seeing all the logs are being printed. Is this the expected behavior?Users want to only log the
ERRORbut that doesn't seem like an option today? Is there any configuration that we're missing.cc @tam7t
What did you expect to happen:
Anything else you would like to add:
[Miscellaneous information that will assist in solving the issue.]