Honor stderrthreshold when logtostderr is enabled

[pierluigilenoci]

Summary

• Update k8s.io/klog/v2 to v2.140.0 which includes the fix for kubernetes/klog#212
• Opt into the new klog behavior by setting -legacy_stderr_threshold_behavior=false
• Set -stderrthreshold=INFO to preserve backward-compatible behavior
• Users can now override -stderrthreshold to WARNING or ERROR to reduce stderr noise

Fixes #128

Ref: kubernetes/klog#212, kubernetes/klog#432

[k8s-ci-robot]

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

[pierluigilenoci]

/test all

[pierluigilenoci]

cc @leakingtapan @mskanth972 — would you be able to review this when you get a chance? This opts into the klog fix for kubernetes/klog#212 so that -stderrthreshold is honored even when -logtostderr=true.

[pierluigilenoci]

Gentle ping @leakingtapan @mskanth972 — would you be able to review when you get a chance? This is a one-line fix for kubernetes/klog#432. Thank you!

[DavidXU12345]

I did e2e tests from my end and verified that if we set stderrthreshold to WARNING,

• Before the fix, INFO level logs still get printed out
• After the fix, all INFO level logs will not be printed after the fix.

kubectl patch ds efs-csi-node -n kube-system --type=json -p='[
  {"op":"add","path":"/spec/template/spec/containers/0/args/-","value":"--stderrthreshold=WARNING"}
]'
daemonset.apps/efs-csi-node patched

[DavidXU12345]

/lgtm

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: DavidXU12345, pierluigilenoci

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [DavidXU12345]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment