Proxy iptables rule on 0.0.0.0 leads to an infinite loop, use ! 10.0.0.0/8 instead

This happens with AWS ELB; we use the listenIp which is normally 0.0.0.0

But this means that the traffic that is headed for the docker instance is also triggered.
This causes an infinite loop (at least I think that is what happens; kube-proxy rapidly
runs out of open files)

Instead, we can match on ! 10.0.0.0/8, which means we match true public IPs, but
not internal IPs