+++ This bug was initially created as a clone of Bug #1810814 +++ In an IPv6 Azure cluster, there will be error messages in the ovnkube-node logs like: time="2020-03-05T21:14:51Z" level=error msg="Error in modifying service: failed to add iptables nat/OVN-KUBE-NODEPORT rule \"-d 2603:1030:b:3::1f -p TCP --dport 80 -j DNAT --to-destination fd99::2:31863\": running [/usr/sbin/ip6tables -t nat -C OVN-KUBE-NODEPORT -d 2603:1030:b:3::1f -p TCP --dport 80 -j DNAT --to-destination fd99::2:31863 --wait]: exit status 2: ip6tables v1.8.2 (nf_tables): Bad IP address \"fd99::2:31863\"\n\nTry `ip6tables -h' or 'ip6tables --help' for more information.\n" (The "Bad IP address" being the relevant bit.) We need to fix those (by putting brackets around the IP).
This fix is only useful if cloud loadbalancers are otherwise working with IPv6, but they aren't in 4.3, and we don't care about this any more (in 4.3).