There is an effort in OVN-Kubernetes to support user defined networks for namespaces, it brings flexibility for tenant workloads to use either default cluster network or user defined network as their K8s primary networking.
So there is a need for enhancing EgressIP component to support when pod traffic is using an user defined overlay network. This overlay network can be either L2 or L3. The node's egress interface can be either OVN-Kubernetes managed or unmanaged interface.
The overall design changes for EgressIP is described in this PR which is under review. We still need a separate design document specifically for EgressIP describing more information about the design.
Why is this needed?
This enhancement request is mainly to capture nitty gritty details of design changes going to be made into EgressIP component and how things work seamlessly supporting both default cluster network or user defined networks.
What would you like to be added?
There is an effort in OVN-Kubernetes to support user defined networks for namespaces, it brings flexibility for tenant workloads to use either default cluster network or user defined network as their K8s primary networking. So there is a need for enhancing EgressIP component to support when pod traffic is using an user defined overlay network. This overlay network can be either L2 or L3. The node's egress interface can be either OVN-Kubernetes managed or unmanaged interface. The overall design changes for EgressIP is described in this PR which is under review. We still need a separate design document specifically for EgressIP describing more information about the design.
Why is this needed?
This enhancement request is mainly to capture nitty gritty details of design changes going to be made into EgressIP component and how things work seamlessly supporting both default cluster network or user defined networks.