Configure klog output severity by flags

[cute-rui]

/kind support

I tried to make klog only output severity above warn to console, but only found verbosity settings. Is there a way to adjust klog flags to change the log output severity level, so that only warnings, errors messages are logged to the console? Any guidance on achieving this would be greatly appreciated.

[pohly]

Perhaps you can use https://pkg.go.dev/k8s.io/klog/v2#SetOutputBySeverity?

[logicalhan]

/kind support
/triage accepted

[cute-rui]

Perhaps you can use https://pkg.go.dev/k8s.io/klog/v2#SetOutputBySeverity?

The issue is that what I deployed is a third-party project that can only be modified through klog flags. For example, the metrics-scraper module of the Kubernetes dashboard outputs unnecessary heartbeat messages, and modifying the code to address this is tedious.

[pohly]

There are no klog flags for what you want to achieve and given that klog is considered in feature freeze, I also don't want to add some.

If you find that some component is too verbose at normal production verbosity levels (-v=2 in Kubernetes), then the best approach is to bring that up with the maintainers of that component.

[k8s-triage-robot]

This issue has not been updated in over 1 year, and should be re-triaged.

You can:

• Confirm that this issue is still relevant with /triage accepted (org members only)
• Close this issue with /close

For more details on the triage process, see https://www.kubernetes.dev/docs/guide/issue-triage/

/remove-triage accepted

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale