After gateway failover sometimes an extra 220 routing table (strongswan) will be left and break connectivity

[mangelajo]

After a gateway failover, a worker that previously was a master gateway would leave some entries in routing table 220 (strongswan) which take precedence to the default routing rules.

This will make connectivity to the remote cluster from such node. This breaks the E2E tests sometimes.

NOTE: 10.246.224.3 is a remote cluster pod

root@cluster2-worker:/# ip r get 10.246.224.3
10.246.224.3 via 172.17.0.6 dev eth0 table 220 src 172.17.0.5 uid 0

root@cluster2-worker:/# ip r
default via 172.17.0.1 dev eth0
10.245.0.0/16 dev weave proto kernel scope link src 10.245.0.1
10.246.0.0/16 via 240.17.0.8 dev vx-submariner proto static
100.96.0.0/16 via 240.17.0.8 dev vx-submariner proto static
172.17.0.0/16 dev eth0 proto kernel scope link src 172.17.0.5
240.0.0.0/8 dev vx-submariner proto kernel scope link src 240.17.0.5

root@cluster2-worker:/# ip r show table 220
10.246.0.0/16 via 172.17.0.6 dev eth0 proto static src 172.17.0.5
100.96.0.0/16 via 172.17.0.6 dev eth0 proto static src 172.17.0.5
172.17.0.6 via 172.17.0.6 dev eth0 proto static src 172.17.0.5

fixed:

root@cluster2-worker:/# ip r flush table 220
root@cluster2-worker:/# ip r get 10.246.224.3
10.246.224.3 via 240.17.0.8 dev vx-submariner src 240.17.0.5 uid 0