Allow FlexibleIPAM to work in encap mode, so it would work with EgressIP

[jsalatiel]

Describe the problem/challenge you have The current implementation of FlexibleIPAM requires Linux Nodes, with IPv4, system OVS datapath type, and noEncap, noSNAT traffic mode. That means that I can not use EgressIP while still being able to assign some specific ippool for namespaces.

Describe the solution you'd like I would like to be able to use FlexibleIPAM with the default antrea configuration ( that enables egressIP by default )

Anything else you would like to add? I also use ServiceExternalIP and I am not sure it would impact that too.

[jianjuns]

@gran-vmv : I remember you did consider supporting encap mode with FlexibleIPAM? Could you share thoughts here?

[gran-vmv]

@gran-vmv : I remember you did consider supporting encap mode with FlexibleIPAM? Could you share thoughts here?

According to current FlexibleIPAM design, we're unable to provide EncapMode in an easy way, because EncapMode requires Antrea to calculate next-hop for inter-Node traffics, which is handled by L2 network currently. If Antrea calculates next-hop, it will require antrea-agent to cache all Pod-Node-VLAN mapping and greatly increase the complexity of OVS flows to set the tunnel-dst according to packet dst-ip and vlan-id.

Maybe we can consider to integrate EgressIP feature into external GW

[github-actions[bot]]

This issue is stale because it has been open 90 days with no activity. Remove stale label or comment, or this will be closed in 90 days

[jsalatiel]

/remove-stale

[github-actions[bot]]

This issue is stale because it has been open 90 days with no activity. Remove stale label or comment, or this will be closed in 90 days