Depending on how we implement dual stack VIPs, we may need to make changes to how baremetal-runtimecfg templates config files. Currently it can only take a single value for both the api and ingress VIPs, and if we decide to use a single keepalived config then runtimecfg will need to be able to handle taking multiple VIPs as input and also have appropriate logic changes to handle them. Currently runtimecfg has a number of places that it looks at "the" api VIP to determine whether to use v4 or v6 behavior. If "the" VIP becomes two VIPs that won't work.

I'm not story pointing this because the amount of work (if any) will depend on the results of other design discussions.