Understanding is there has been previous investigation into this issue between deads@redhat.com, mkowalsk@redhat.com and davegord@redhat.com regarding jobs like origin-master-e2e-metal-ipi-ovn showing disruption due to on prem load balancer readiness configurations not matching kube-apiserver expectations.  Which in turn leads to endpoints not ready for service to remain in service and record disruption.

This bug is to track the work getting the configuration standardized along with accompanying work providing timeline intervals surfacing the issues.