Open roshnihp opened 4 years ago
It looks like Packet supports load-balancing through ECMP and BGP.
If we can set up the LBs (L3fwd) with BGP, I think the rest of the use-case (L2 bridge) and client PODs should be fairly easy to sort out.
Do you know of any existing work with the forwarder, or do we need to create something "from scratch" to work this out?
Wwe are working on an example implementation. We could do PR once that is done.
Description The main scope is to get VPN/Traffic separation and end to end external connectivity by dedicating a specific interface to application pods. The additional interface in the pods must be externally accessible using a VIP (Virtual IP) address.
How Distributed Bridge domain Network Service will establish point to point connection to all application pods using bridge. A Network Service Endpoint (Layer 3 Forwarder NSE) with loadbalancing functionality could loadbalance the incoming traffic from Gateway router to the application pods via Bridge Domain NSE. Test bed could use software router to simulate gateway router. The Gateway router will ECMP the incoming traffic to nodes with L3 forwarder NSE.