-
Notifications
You must be signed in to change notification settings - Fork 931
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.
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
Metallb in l2 mode should publish an event indicating which node is advertising a vip. #430
Comments
This could also help to isolate issues where in l2 mode arp is taking longer to timeout on re election :) |
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:
|
Fixed in 5cc6e23, just forgot to link it via the commit msg. Will be in next release. |
How does this work? I've updated to MetalLB 0.8.0 and I can't see any events published in any of my LoadBalanced Services. |
Is this Event periodically published? Events are retained for 1h by default, and am not sure if this Event is published more frequently. I am trying to find the Speaker for a service that is rather old, and nothing is showing in the describe. |
Hi @jmlogan , the event is published only when the speaker association is done (here). If nothing changes in the service or in the list of endpoints, I believe the event is not produced (and in any case, I am sure it's not produced periodically). |
Just to add more info, the association between service / node / lbip is avaliable as prometheus metric too : Line 284 in 5d23698
|
so, how to know the leader is? Is there doc for this? |
|
The metric is called |
Please note we also have serviceL2Status now: https://github.com/metallb/metallb/blob/main/api/v1beta1/servicel2status_types.go |
Feature Request:
in L2 mode it would help to understand what node is servicing a given vip.
Ideally, the speaker could publish an event to the service object indicating the node that has "won" the election for 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.
The text was updated successfully, but these errors were encountered: