Extended.[k8s.io] Service endpoints latency should not be very high [Conformance]

[bparees]

[k8s.io] Service endpoints latency
/go/src/github.com/openshift/origin/_output/local/go/src/github.com/openshift/origin/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:826
  should not be very high [Conformance] [It]
  /go/src/github.com/openshift/origin/_output/local/go/src/github.com/openshift/origin/vendor/k8s.io/kubernetes/test/e2e/service_latency.go:116

  Not all RC/pod/service trials succeeded: got 1 errors
  50, 90, 99 percentiles: 190.11984ms 319.247801ms 398.195681ms

  /go/src/github.com/openshift/origin/_output/local/go/src/github.com/openshift/origin/vendor/k8s.io/kubernetes/test/e2e/service_latency.go:114

https://ci.openshift.redhat.com/jenkins/job/test_pull_requests_origin_conformance/10957/

[derekwaynecarr]

See corresponding flake upstream:
kubernetes/kubernetes#30632

I am reducing priority to align with upstream priority as it appeared to not happen for 12 consecutive days during k8s 1.5 release process.

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale