changing CARP VIP address does not update outbound NAT interface IP
In my testing, on a 2 node HA cluster running 22.05.a.20220426.1313, if you change the Virtual IP, it is properly synced to the backup node, but the manual outbound NAT rule is not updated, so things break slightly. I am not sure if this is by design, but since you are selecting the IP by interface name, it seems like it would intuitively work the way other aliases work and "follow" changes to the chosen named VIP.
Updated by Jim Pingle 4 months ago
- Priority changed from Normal to Very Low
This isn't necessarily going to be desirable or helpful. The two are not necessarily related even if they share the address in common at some point. Someone may want to change a VIP without changing NAT or vice versa. At some point the user has to be aware of the impact of their changes rather than attempting to automate everything and breaking other workflows.
Maybe it could prompt them to take further action on change but I'm hesitant to automate this.