Ezequiel Farji

Hi, I'm having a similar issue as the one described in this bug, but my problem is when running the following code after acquiring the lease: ``` err = cluster.Network.AddIP()...

Sorry, this is the file: https://github.com/kube-vip/kube-vip/blob/8af0391bc910ddd327a69c69632a411a96c5f807/pkg/cluster/service.go#L49-L52 In my case, the default device is getting recreated on all nodes; when that happens, the leader instance of kube-vip gets correctly restarted, but...

Hi @thebsdbox were you able to check this issue? IMO leader election should be lost in case of recreating the default device and that should probably fix this problem

Hi, I'm having the same issue and the solution proposed by @ErikEngerd seems fine; the namespace on involvedObject field must not be specified for cluster wide objects for Kubernetes to...