This issue was first observed when running kubernetes 1.8 on DC/OS. In kubernetes 1.8, kube-proxy has experimental support for IPVS. However, even if one is not using kube-proxy in IPVS mode, it still flushes all the IPVS entries which breaks DC/OS L4LB. While the main issue should get fixed with kube-proxy still DC/OS L4LB should check the correctness of its configuration periodically. It will help if some other application touches/changes the IPVS configuration.