kube-proxy reference showing wrong logging flags

[manuelbuil]

Hi,

By grepping on the logging related kube-proxy flags, I see:

* log-flush-frequency
* log-json-info-buffer-size
* log-json-split-stream
* logging-format

However, in the reference docs there are many more:

* alsologtostderr
* log_backtrace_at 
* log_dir
* log_file
* log_file_max_size
* logtostderr

If I use any of those, as expected, I get an error: Error: unknown flag:

[sftim]

/kind bug /sig docs /language en

[sftim]

/triage accepted /priority backlog

[kundan2707]

/assign

[k8s-ci-robot]

@kundan2707: The label(s) sig/netwotk cannot be applied, because the repository doesn't have them.

In response to [this](https://github.com/kubernetes/website/issues/44750#issuecomment-2203493205): >/sig netwotk Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes-sigs/prow](https://github.com/kubernetes-sigs/prow/issues/new?title=Prow%20issue:) repository.

[kundan2707]

/sig network

[mengjiao-liu]

Many log flags have indeed been removed in the kube-proxy. See the following pages for more details:

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

[kundan2707]

@mengjiao-liu i have considered removed flag too and updated as per latest available flags

[mengjiao-liu]

Great! the above information is for reference only.