Developer story

As a WMCO developer, I want pass the `kube-proxy` configuration using a config file, so that deprecated log entries does note shows during kube-proxy startup.

Description

kube-proxy.exe logs shows:

WARNING: all flags other than --config, --write-config-to, and --cleanup are deprecated. Please begin using a config file ASAP.

For kube-proxy all flags other than --config, --write-config-to, and --cleanup are deprecated. Move the existing configuration flags into a KubeProxyConfiguration config file and use just the --config flag.

Required

Avoid using kube-proxy all flags other than --config

Nice to have

Document any custom configuration in the config file

Engineering Details

Refactor the kubeProxyConfiguration in WMCO source code and encapsulate using KubeProxyConfiguration in combination with `--config` flag.

Be careful to avoid any issues similar to issue #128, where Kubernetes uses different defaults when a --config file is used.

Command line docs: https://kubernetes.io/docs/reference/command-line-tools-reference/kube-proxy/

Config file docs: https://github.com/kubernetes/kubernetes/blob/master/staging/src/k8s.io/kube-proxy/config/v1alpha1/types.go

Upstream issue for documentation about kube-proxy ConfigFile: https://github.com/kubernetes/kubernetes/issues/50041

Acceptance Criteria

• WARNING message does not appears in the logs
• kube-proxy works as expected