text: Title: [Flaky Test] [sig-network] ESIPP [Slow] should work for type=LoadBalancer
  Body: <!-- Please only use this template for submitting reports about flaky tests or jobs (pass or fail with no underlying change in code) in Kubernetes CI -->
  
  **Which jobs are flaking**:
  
  `gce-master-scale-correctness (ci-kubernetes-e2e-gce-scale-correctness)`
  
  **Which test(s) are flaking**:
  
  `[sig-network] ESIPP [Slow] should work for type=LoadBalancer`
  
  **Testgrid link**:
  
  https://testgrid.k8s.io/sig-release-master-informing#gce-master-scale-correctness
  
  **Reason for failure**:
  
  ```
  /go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/network/service.go:3029
  Aug 26 13:49:40.880: Unexpected error:
      <*errors.errorString | 0xc00021a200>: {
          s: "timed out waiting for the condition",
      }
      timed out waiting for the condition
  occurred
  /go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/network/utils.go:745
  ```
  
  **Anything else we need to know**:
  
  This test recently had a flake described in https://github.com/kubernetes/kubernetes/issues/93341 that was fixed in https://github.com/kubernetes/kubernetes/pull/92163. I believe this failure is different, and could be infrastructure related.
  
  /cc @kubernetes/ci-signal @wojtek-t @knight42 
  /sig network
  /priority important-soon
  /milestone v1.20
  