Marcel Fest

@m198799 thanks for writing this comment this is exactly the reason why and it is debatable what should be the correct target for the lease. Just switching it to the...

@m198799 Please check #1129 and also maybe try the new `main` build which correctly handles multiple Services with the same IP now.

@p-strusiewiczsurmacki-mobica does this also enable us to share the cp-lock with the svc-lock to enable the cp + lb mode on micro clusters?

@p-strusiewiczsurmacki-mobica ah it is not cross namespace ref for the lease. So it would work if someone runs it in vip_leaderelection mode enabling cp and svc and then pointing the...

This would at least also allow the micro clusters :)

@p-strusiewiczsurmacki-mobica, can we first merge the common Lease and make micro clusters a separate feature? :)

@SebPlv @cyclinder @Raboo did you try one of the 0.9.x releases?

Can you provide both services as yamls? That would be easier to find out your exact problem. Additionally the deployment yaml of your kube-vip daemonset would also help.

If you configure the same IP on both Services. Kube-VIP cannot decide if you want to share the IP or not. When you want to share the IP you need...

The feature you are requesting is source based routing for the LoadBalancer implementation. @thebsdbox this would be a nice feature, but I think the configuration for SBR should not be...