fix: honor klog -stderrthreshold even when -logtostderr is true

[pierluigilenoci]

What changed

klog v2 defaults -logtostderr to true, which silently ignores -stderrthreshold — all log levels go to stderr unconditionally. This has been an open issue since 2020.

klog v2.140.0 introduced a fix behind an opt-in flag (legacy_stderr_threshold_behavior). This PR bumps klog to v2.140.0 and enables the fix in both entry points (cmd/addon-manager/main.go and pkg/config/args_log.go) so that -stderrthreshold is honored, while preserving the current default behavior.

References

• Upstream issue: stderrthreshold not honored when logtostderr is set kubernetes/klog#212
• Upstream fix: feat: fix stderrthreshold not honored when logtostderr is set (#212) + two new flags kubernetes/klog#432

---

Summary by cubic

Honor -stderrthreshold when -logtostderr=true by enabling klog’s new behavior. Default stderr level stays at INFO unless overridden.

• Bug Fixes

  • Set legacy_stderr_threshold_behavior=false and default stderrthreshold=INFO in cmd/addon-manager/main.go and pkg/config/args_log.go; add unit test for AddLogFlags and harden it with require.NotNil to avoid nil deref.

• Dependencies

  • Bump k8s.io/klog/v2 to v2.140.0.

^{Written for commit 1e01bde. Summary will update on new commits.}

[cubic-dev-ai]

No issues found across 4 files

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 9.89%. Comparing base (2b04dd4) to head (1e01bde).

Additional details and impacted files

@@            Coverage Diff            @@
##           master    #168      +/-   ##
=========================================
- Coverage   10.51%   9.89%   -0.63%     
=========================================
  Files          49      49              
  Lines        7029    6501     -528     
=========================================
- Hits          739     643      -96     
+ Misses       6238    5806     -432     
  Partials       52      52              

Flag	Coverage Δ
unit-test	9.89% <100.00%> (-0.63%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[pierluigilenoci]

Added a unit test for AddLogFlags in pkg/config/args_log_test.go to cover the new klog flag overrides (legacy_stderr_threshold_behavior and stderrthreshold). This should satisfy the codecov patch coverage threshold.

Regarding the e2e-ocm-addon-cluster-gateway failure — this is a pre-existing infrastructure issue (the addon service returns HTTP 503 / ServiceUnavailable). The same test has been consistently failing on other branches as well (e.g. user/amisingh-ocm-debug runs from July 2025). This failure is unrelated to the changes in this PR.

[cubic-dev-ai]

1 issue found across 1 file (changes from recent commits).

_{Reply with feedback, questions, or to request a fix. Tag @cubic-dev-ai to re-run a review.}

[pierluigilenoci]

@yue9944882 @Somefive — friendly ping, could one of you review this when you get a chance? The e2e-ocm-addon-cluster-gateway failure is a pre-existing infrastructure flake (same failure on unrelated branches). All other CI checks pass. Thanks!

[pierluigilenoci]

Hi — friendly follow-up. CI is green, merge state is clean, and all checks are passing. Would you be able to review when you get a chance? Thank you!

[pierluigilenoci]

Hi @yue9944882 @Somefive — friendly ping on this PR. All CI checks are green and the branch is up-to-date. Would you be willing to take a look when you have a chance? Happy to address any feedback. Thank you!