Kube-VIP ARPs conflicting VIP information

[dacjames]

Kube-VIP ARPs conflicting VIP information

[lubronzhan]

You enabled svc_election and this is only for advertising service type lb, so it's expected that each service will have its own leader, and they acquires leader on each kube-vip independently, so there could be 2 services acquiring leader on same node or on different node.
Relevant code is here https://github.com/kube-vip/kube-vip/blob/main/pkg/manager/servicesLeader.go#L18

It's possible that the previous leader didn't exist correctly, so two leader are ARPing for same service, but it's possible that two service type lbs got assigned with same IP, so two node are reporting the same IP, this is also worth checking.

I would recommend using newer kube-vip since many refactoring have been made, and please upload kube-vip log for each of the leader when this issue happens, at least we could check if it's ARPing for same service or not

[dacjames]

@lubronzhan Thanks for the help!

there could be 2 services acquiring leader on same node or on different node.

How do I check for this condition and prevent it's occurrence?

Will do on the update.

[lubronzhan]

there could be 2 services acquiring leader on same node or on different node.
How do I check for this condition and prevent it's occurrence?

This is expected, since you enabled svc_election, each service will has its own leader. and it should work as long as two services have different loadbalancerIP. So I don't think you want to prevent its occurrence. Unless you have two services share the same loadbalancerIP.

I would need more log to help understand the issue. Please update once you run into that again.

Thanks

[dacjames]

Ack on the per-service load balancer. I was getting confused on nodes vs service leader but I think I get it now. My understanding is that each service (differentiated by loadbalancerIP) should have a unique leader. Which is what appears not to have happened as two instances were ARPing the same loadbalancerIP to different interfaces simultaneously.

Unless you have two services share the same loadbalancerIP.

That is not the case now but might have occurred transiently and been subsequently corrected.

Working on an update and will provide additional logs.