Allow to configure healthzBindAddress for kube-proxy

[dodgex]

Is your feature request related to a problem? Please describe.

I'm evaluating k0s for my home lab and want to bind everything related to k0s to a specific port.

Currently it is not possible to configure the --healthz-bind-address as this option is ignored when a config file is specified by --config (see docs) which is the case using the kube-proxy ConfigMap. But the ConfigMap has an empty value hardcoded.

Describe the solution you would like

Add a healthzBindAddress to k0s.yaml similar to what #2378 did for metricsBindAddress.

Describe alternatives you've considered

Blocking the access to the port via iptables, or patch the ConfigMap (seems to work for now, but I do not know how consistent this is).

Additional context

No response

[dodgex]

When you can confirm, that this change is "as simple as" adding the option similar to #2378 for metricsBindAddress, I am willing to open a PR.

[jnummelin]

https://docs.k0sproject.io/stable/configuration/#specnetworkkubeproxy

You should be able to do this with something like:

spec:
  network:
    kubeProxy:
      extraArgs:
        healthz-bind-address: 1.2.3.4:5555

[dodgex]

Hey @jnummelin,

unfortunately, I can't. As I written in the issue above, the --healthz-bind-address arg is ignored if a config file is specified by --config, and that is what happens in k0s.

See --healthz-bind-address at https://kubernetes.io/docs/reference/command-line-tools-reference/kube-proxy/ (unfortunately, they do not have anchors for the options, otherwise I would have directly linked to the option)