Douglas Land

@murali-reddy yep, the quagga router is part of sg-2e55565c, the same security group as the kubernetes nodes, as well as sharing the same subnet/az with 1/3 of the nodes and...

Interesting, sorry I'm kind of a BGP n00b to know what this means: > Peer AS Up/Down State |#Received Accepted >172.30.37.50 64512 6d 13:01:15 Establ | 1 1 >172.30.48.223 64512...

for good measure here's one of the nodes failing updates: > Peer AS Up/Down State |#Received Accepted > 172.30.37.50 64512 6d 13:07:08 Establ | 1 1 > 172.30.48.223 64512 6d...

Sorry is it maybe port 179, minus the 0? > root@ip-172-30-52-146:~# netstat -lntp > Active Internet connections (only servers) > Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name...

I was in the middle of testing something else and the IPs in the cluster are different, but the situation is the same.. The quagga router is now at 172.30.98.97....

Hi @murali-reddy, any chance these warnings provide any clues? Thanks!

Great! Thank you so much @murali-reddy!

I understand your point but I guess I'm confused about how the kube-router nodes are handling this since they're talking across subnets as well?

As a side note, I would think a multi-az kubernetes cluster is a very typical configuration. Are there other topologies that would provide me with direct service and pod routing...

We have a VPN endpoint terminating in our VPC which allows us to route directly to addresses within the VPC subnet. We're currently using flannel and I've set up a...