From 15bd679b03edeba783bd20f4ae3aca63cb0faac3 Mon Sep 17 00:00:00 2001 From: Lion-Wei Date: Mon, 21 Aug 2017 11:05:29 +0800 Subject: [PATCH] Update README.md --- docs/faq/README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/faq/README.md b/docs/faq/README.md index 9d0e524c9..fc3bfd982 100644 --- a/docs/faq/README.md +++ b/docs/faq/README.md @@ -103,8 +103,8 @@ Testing for the Ingress controllers is divided between: [per release-branch e2e](https://k8s-testgrid.appspot.com/google-gce#gci-gce-ingress-1.5) The configuration for jenkins e2e tests are located [here](https://github.com/kubernetes/test-infra). -The Ingress E2Es are located [here](https://github.com/kubernetes/kubernetes/blob/master/test/e2e/ingress.go), -each controller added to that suite must consistently pass the [conformance suite](https://github.com/kubernetes/kubernetes/blob/master/test/e2e/ingress_utils.go#L112). +The Ingress E2Es are located [here](https://github.com/kubernetes/kubernetes/blob/master/test/e2e/network/ingress.go), +each controller added to that suite must consistently pass the [conformance suite](https://github.com/kubernetes/kubernetes/blob/master/test/e2e/framework/ingress_utils.go#L129). ## An Ingress controller E2E is failing, what should I do?