SKALA NETWORKS
SKALA NETWORKS
That sounds like a good idea, a few questions on my part: - EIPs need to be part of the "external subnet", correct? If yes, that would be limiting. Ideally...
My understanding is ARP would still be the protocol used to get the gateway to know where to send the traffic. Would it not be more optimal to have the...
> As far as I know, the vpc nat gateway pod has two interfaces, that is, eth0 and net1. One of them has an "internal" ip address which belongs to...
Yeah from what I read in the documentation, it doesn't seem to fit completely my usecases. I'll look at the code regarding everything BGP related and see how we could...
I'm more interested about the ability to announce any IP I own from any subnet I own to the internet from the NAT GW, and not be stuck with the...
I'm working on a PR for this, I refactored the BGP part so it can work for EIPs too. I put the speaker inside a nat gateway pod and realized...
Drawback is the logic for the BGP speaker each refresh cycle is: - pull all routes announced by our speaker - compute a huge slice of everything we need to...
Note: - Nexthop is the "primary IP" of the NAT GW - Forwarding to nexthop is still ensured by L2 with ARP. If the pod moves, the routes announced are...
Do we want to do that though? My personal opinion after thinking about it is that carrying a BGP speaker for each nat gw would make the whole process kinda...
Good point on using the speaker has a trojan horse to get kube-ovn's code to run inside the NAT gateway. That'll be useful later down the road for getting a...