v0.2.0-beta.10

Enhancements

• Support to choose a different port for BGP than default value of 179. This opens up possibility to run a different BGP implementation (like for e.g. BIRD) in conjunction with GoBGP running as part of kube-router

   An e.g use-case: https://kubernetes.slack.com/archives/C8DCQGTSB/p1533650593000416
  

• In case of multiple uplinks to different external peers, next-hop used should be appropriate local IP (instead of hard code node IP as earlier). --override-nexthop basically overrides the next hop configured in local RIB with appropriate local ip as next hop when advertising routes to the BGP peers.

• Support for user configurable list of local IP address on which BGP server should listen. This is important in case of nodes with multiple interfaces and multiple external peers.

Changelog

01ec883 prevent IPIP tunnel creation when --override-nexthop=ture (#518)
1db83ad Added support for custom BGP ports with 179 still being default (#492) (#493)
86ba784 Introduces the option --override-nexthop, to override the next hop used in advertised routes (#502)
b76d22f [jjo] ipAddrDel(): also delete VIP local rt addition (#514)
624c74f issue-385: make it optional on which ip address BGP server listens (#473)
94e163b update BGP export policies on endpoints add event (#508)
85d8df4 Improve health check for cache synchronization (#498)
e2ee6a7 Fix blackholing of traffic when using local traffic policy / annotation (#495)
8bed56f processing k8s version for NPC (#488)
f340218 fix case where 1 min unintended delay is added when checking for tunnel interface to come ip in pod (#472)

thanks @jjo @johanot @jimmy-zh @jdconti for the contributions.