I wonder if we should just set `bind_ip` to '::' and stop trying to lock it down to the load balancer instance management network. This would make this much simpler and less error prone.
The low level socket calls made to set up the listener [0] will bind the socket to both IPv4 and IPv6 when given an v6 address, and use the v4-mapped-on-v6 address type to allow the program to work with both [1].
I wonder if we should just set `bind_ip` to '::' and stop trying to lock it down to the load balancer instance management network. This would make this much simpler and less error prone.
The low level socket calls made to set up the listener [0] will bind the socket to both IPv4 and IPv6 when given an v6 address, and use the v4-mapped-on-v6 address type to allow the program to work with both [1].
0: https:/ /github. com/openstack/ octavia/ blob/3c5bbbc189 efe9f3ed4caae04 a23d7a13718d368 /octavia/ amphorae/ drivers/ health/ heartbeat_ udp.py# L62-L86 /git.kernel. org/pub/ scm/docs/ man-pages/ man-pages. git/tree/ man7/ipv6. 7?id=902460e768 b5c19d693f7ef87 979b1613800cddf #n130
1: https:/