"monitor ip address" shows dozens of adding and removings of clusterIp per second

[Luc Derheld]

Is it normal, that a clusterip out of an metallb address pool is added frequently per second to an network device and then deleted?

Is this how metallb works behind the scenes to distribute an actual mac address to broadcast? Or is something wrong with my cluster setup?

This what happens on control1 node:

root@control1:/# ip monitor address
Deleted 2: eth0    inet 10.7.0.201/32 scope global eth0
       valid_lft forever preferred_lft forever
2: eth0    inet 10.7.0.201/32 scope global eth0
       valid_lft forever preferred_lft forever
Deleted 2: eth0    inet 10.7.0.201/32 scope global eth0
       valid_lft forever preferred_lft forever
2: eth0    inet 10.7.0.201/32 scope global eth0
       valid_lft forever preferred_lft forever
Deleted 2: eth0    inet 10.7.0.201/32 scope global eth0
       valid_lft forever preferred_lft forever
2: eth0    inet 10.7.0.201/32 scope global eth0
       valid_lft forever preferred_lft forever
Deleted 2: eth0    inet 10.7.0.201/32 scope global eth0
       valid_lft forever preferred_lft forever
2: eth0    inet 10.7.0.201/32 scope global eth0
       valid_lft forever preferred_lft forever
[...]

All control and worker nodes have assigned this ip on kube-ipvs0 interface.

4: kube-ipvs0: <BROADCAST,NOARP> mtu 1500 qdisc noop state DOWN group default
    link/ether [...] brd ff:ff:ff:ff:ff:ff
[...]
    inet 10.7.0.201/32 scope global kube-ipvs0
       valid_lft forever preferred_lft forever