Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

v1.5.0 external bgp connection fails #1391

Closed
rkojedzinszky opened this issue Nov 2, 2022 · 1 comment · Fixed by #1392
Closed

v1.5.0 external bgp connection fails #1391

rkojedzinszky opened this issue Nov 2, 2022 · 1 comment · Fixed by #1392
Labels
bug

Comments

@rkojedzinszky
Copy link
Contributor

What happened?
Upgraded from v1.4 to v1.5, and external bgp peer connections failed to estabilish.

What did you expect to happen?
Expected external bgp sessions to come up as before.

How can we reproduce the behavior you experienced?
Steps to reproduce the behavior:

  1. Have a node with two (or more L3) interfaces, one said to be k8s backbone, and one facing an external router
  2. Annotate the node to have the external bgp configuration
  3. Restart kube-router on node
  4. Observe Mismatched local address log messages in kube-router's log

Additional context
I suspect 184976a causes the change. Perhaps, it would be helpful to specify a localaddress for peers via annotations the same way as other parameters.
@rkojedzinszky rkojedzinszky mentioned this issue Nov 2, 2022
Merged
@aauren
Copy link
Collaborator

aauren commented Nov 2, 2022

Closing this as a duplicate of #1371

@aauren aauren closed this as completed Nov 2, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Support for kube-router.io/peer.localips annotation rkojedzinszky/kube-router
2 participants
@aauren @rkojedzinszky