I went through the changes OpenShift has made for supporting static-egress-ip for external traffic.
It earlier used egress-router for static egress IP, which creates a macvlan interface for static IP. One particular drawback with the legacy egress router is that it creates a new virtual network device which has its own MAC address. This presents a challenge for cloud-based deployments where macvlan traffic might not be compatible. Additionally, it can only route to a limited number of external servers which makes it difficult to use when pods need to contact many external servers sharing the same recognized source IP.
I went through the changes OpenShift has made for supporting static-egress-ip for external traffic.
It earlier used egress-router for static egress IP, which creates a macvlan interface for static IP. One particular drawback with the legacy egress router is that it creates a new virtual network device which has its own MAC address. This presents a challenge for cloud-based deployments where macvlan traffic might not be compatible. Additionally, it can only route to a limited number of external servers which makes it difficult to use when pods need to contact many external servers sharing the same recognized source IP.
Source: https://blog.openshift.com/how-to-enable-static-egress-ip-in-ocp/