Metallb in l2 mode should publish an event indicating which node is advertising a vip.

[mauilion]

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.

[mauilion]

This could also help to isolate issues where in l2 mode arp is taking longer to timeout on re election :)

[zetaab]

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:

{"caller":"main.go:229","event":"serviceAnnounced","ip":"10.1.0.31","msg":"service has IP, announcing","pool":"default","protocol":"layer2","service":"metallb-system/test","ts":"2019-06-26T06:36:35.677084247Z"}

[danderson]

Fixed in 5cc6e23, just forgot to link it via the commit msg. Will be in next release.

[falfaro]

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.

[danderson]

There's a couple of issues with this, #455 and #456 . Together, they prevent publishing these events, and also the event itself contains no information :(

I'll release 0.8.1 later today with fixes.

[jmlogan]

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.

[fedepaol]

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).

[fedepaol]

Just to add more info, the association between service / node / lbip is avaliable as prometheus metric too :

metallb/speaker/main.go

Line 284 in 5d23698

announcing.With(prometheus.Labels{

[zhucan]

so, how to know the leader is? Is there doc for this?

[panpan0000]

so, how to know the leader is? Is there doc for this?

1. find where your LoadBalancer type service , denote it's service AAA in namespace BBB

2. get its event by kubectl -n BBB describe svc AAA

3. you will see event looks like

  Normal  nodeAssigned  7m (x580 over 33d)  metallb-speaker  announcing from node "my-node3" with protocol "layer2"

4. it says "my-node3" is announcing this VIP as metallb speaker leader

[sathieu]

Just to add more info, the association between service / node / lbip is avaliable as prometheus metric too :

metallb/speaker/main.go

Line 284 in 5d23698

announcing.With(prometheus.Labels{

The metric is called metallb_speaker_announced. Thanks!