Default bind address is IPv4 only preventing IPv6 based testing by default

[somemarco]

I was following the Calico IPv6 only setup for Kubernetes which uses this utility for the NetworkPolicy Demo. I used the deployed images also for connectivity testing in the Cluster - given that connections were unsuccessfull I assumed some CNI/Calico/Kubernetes problems - wasting some hours. In the end it was (as previously for other services) simply that it only bind to IPv4 stack.

Question: Would it be not better/possible to bind per default to both IPv4/IPv6 wildcard addresses?

I tripped again on this "only-binds-to-IPv4" as already a couple of times on other services - that's on me but still would be nice if the default would also cover IPv6.

Workaround for the Network Policy Demo manifests is to supplement the command arguments with --http-address=::.