remove deprecated klog flags

[pohly]

What would you like to be added:

At some point we can remove the legacy klog flags. This change includes:

• removing the command line check in component-base/logs/validation.go
• removing the "unsupported flags" warning from the --logging-format help text
• adding a remark for -vmodule that it only works for text output

Why is this needed:

https://github.com/kubernetes/enhancements/tree/master/keps/sig-instrumentation/2845-deprecate-klog-specific-flags-in-k8s-components

[shiva1333]

/sig instrumentation
/wg structured-logging

[shiva1333]

@pohly please feel free to assign me, I've bandwidth to pick this

[pohly]

It's much too early to work on this. 😁

We first must mark the flags as deprecated (#105042) then in Kubernetes 1.26 (?) we can remove them.

[shiva1333]

Okay got it

[logicalhan]

/triage accepted
/assign @serathius

[k8s-triage-robot]

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

This bot triages issues and PRs 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 or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

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

/lifecycle stale

[serathius]

/lifecycle frozen

[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

[serathius]

Don't have capacity to work on this.

[pohly]

/triage accepted
/assign @shivanshu1333

@shivanshu1333: you said that you wanted to work on this - are you still available?

We might be able to do this for 1.27, but I haven't checked.

[shiva1333]

Okay, I'll pick it up...

[pohly]

This issue was resolved via #112120 which was already merged for 1.26! I think we forgot about that when re-triaging this issue...

/close

[k8s-ci-robot]

@pohly: Closing this issue.

In response to this:

This issue was resolved via #112120 which was already merged for 1.26! I think we forgot about that when re-triaging this issue...

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.