### What would you like to be added?

>  `--healthz-bind-address` `ipport`     Default: 0.0.0.0:10256
--
  | The IP address and port for the health check server to serve on, defaulting to "0.0.0.0:10256" (if --bind-address is unset or IPv4), or "[::]:10256" (if --bind-address is IPv6). Set empty to disable. This parameter is ignored if a config file is specified by `--config`.

The documentation suggests that the bind address is singular and that it's either of the IPv4 or IPv6 family. I think that's doubtful, `0.0.0.0` and `::` also bind to both families in `kube-apiserver`. Fix the docs (but see *) or fix the implementation.

### Why is this needed?

This artificial limitation makes it unpredictable where the healthz socket listens when running a dual-stack cluster. 
*: It is particularly problematic and not fixable as a docs fix when the user wants to listen on loopback addresses for both  families, since there's no notation for that, unlike 'all addresses' (0.0.0.0 and ::).
`kube-proxy`'s `--healthz-bind-address` should support IPv4 and IPv6 simultaneously (dual stack)
This is a GitHub Issue
repo:kubernetes
owner:kubernetes
Title : `kube-proxy`'s `--healthz-bind-address` should support IPv4 and IPv6 simultaneously (dual stack)
Issue date:

--- start body ---
### What would you like to be added?

>  `--healthz-bind-address` `ipport`     Default: 0.0.0.0:10256
--
  | The IP address and port for the health check server to serve on, defaulting to "0.0.0.0:10256" (if --bind-address is unset or IPv4), or "[::]:10256" (if --bind-address is IPv6). Set empty to disable. This parameter is ignored if a config file is specified by `--config`.

The documentation suggests that the bind address is singular and that it's either of the IPv4 or IPv6 family. I think that's doubtful, `0.0.0.0` and `::` also bind to both families in `kube-apiserver`. Fix the docs (but see *) or fix the implementation.

### Why is this needed?

This artificial limitation makes it unpredictable where the healthz socket listens when running a dual-stack cluster. 
*: It is particularly problematic and not fixable as a docs fix when the user wants to listen on loopback addresses for both  families, since there's no notation for that, unlike 'all addresses' (0.0.0.0 and ::).
--- end body ---

None