Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
Metallb in l2 mode should publish an event indicating which node is advertising a vip. #430
in L2 mode it would help to understand what node is servicing a given vip.
If we need to move to another node a new event should be published to that service object. So that we can understand that the ip is now served by a different speaker.
This is helpful when trying to understand how l2 mode will interact with the underlying network.
What kind of event you mean? There is already one log message coming when the ip address is active in speaker: https://github.com/danderson/metallb/blob/master/speaker/main.go#L229
it looks like: