Is this a bug report or a feature request?:
Bug, thanks to @jpiper for reporting on slack.
What happened:
If you cause a BGP session to be added to a node by editing node labels, the session comes up, but the existing advertised IPs don't get propagated on that BGP session.
How to reproduce it (as minimally and precisely as possible):
Add a BGP peer to MetalLB's config, with a node selector.
Make the selector match some nodes, so that BGP sessions establish.
Set up a service, verify that speaker is advertising it.
Edit node labels so selector no longer matches. Verify speaker tore down the BGP session.
Edit node labels so selector applies again. Verify speaker sets up BGP session, but does not readvertise IPs.
Environment:
Is this a bug report or a feature request?:
Bug, thanks to @jpiper for reporting on slack.
What happened:
If you cause a BGP session to be added to a node by editing node labels, the session comes up, but the existing advertised IPs don't get propagated on that BGP session.
How to reproduce it (as minimally and precisely as possible):
Add a BGP peer to MetalLB's config, with a node selector.
Make the selector match some nodes, so that BGP sessions establish.
Set up a service, verify that speaker is advertising it.
Edit node labels so selector no longer matches. Verify speaker tore down the BGP session.
Edit node labels so selector applies again. Verify speaker sets up BGP session, but does not readvertise IPs.
Environment: