Skip to content

Conversation

@murali-reddy
Copy link
Member

Modifying the fix done for #385 in commit 8c746b2

Adding an option bgp-listen-all-ip to control on which IP GoBGP server listens on. By default value is false, and GoBGP server will just listen on node IP. When set to true GoBGP server will listen on 0.0.0.0

This flexibility is desinrable when node is multi-homed and GoBGP server can learn routes advertised from different networks.

cc @thoro

@thoro
Copy link
Contributor

thoro commented Jun 21, 2018

Thanks!

@roffe
Copy link
Contributor

roffe commented Jun 21, 2018

i suggest to introduce bgp-listen-address instead that by default use node ip but allows the users to override with the interface of their chosing to allow for further config in corner case scenarios

@murali-reddy
Copy link
Member Author

@roffe makes sense. Will change the PR

@murali-reddy
Copy link
Member Author

I updated the PR to introudce new per node annotation kube-router.io/bgp-local-addresses which lets you to configure local IP addresses on which BGP server should listen.

By default (i.e with no node anntation configures) kube-rotuer continue to configure the GoBGP to listen on the node IP address only.

@murali-reddy murali-reddy merged commit 624c74f into master Aug 13, 2018
@aauren aauren deleted the issue-385 branch September 4, 2023 15:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants