ingress-nginx-helm/test/e2e/framework
Tim Reddehase 018a1e4d94 respond with 503 when there are no endpoints
* related to:
  * https://github.com/kubernetes/ingress-nginx/issues/3070
  * https://github.com/kubernetes/ingress-nginx/issues/3335
* add a 503 test
  * test a service that starts out empty
    (a.k.a. ingress-nginx controller (re-)start)
  * test scaling up (should route traffic accordingly)
  * test scaling down to empty service
  * use custom deployments for scaling test.
* provide a fix by updating the lua table (cache) of the configured backends
  to unset the backend if there are no endpoints available.
2019-02-03 11:43:47 +01:00
..
cleanup.go Include tests in golint checks, fix warnings (#2180) 2018-03-07 08:37:30 -08:00
deployment.go respond with 503 when there are no endpoints 2019-02-03 11:43:47 +01:00
exec.go Update lua configuration_data when number of controller pod change 2018-12-14 13:34:54 -05:00
framework.go Fix --disable-catch-all 2019-01-25 14:53:55 -05:00
grpc_fortune_teller.go Adjust default timeout for e2e tests (#3495) 2018-11-30 18:55:53 -03:00
influxdb.go Adjust default timeout for e2e tests (#3495) 2018-11-30 18:55:53 -03:00
k8s.go Wait for the right number of endpoints (#3497) 2018-11-30 20:17:18 -03:00
logs.go Fix status update in case of connection errors 2018-10-29 13:01:41 -03:00
ssl.go Adjust default timeout for e2e tests (#3495) 2018-11-30 18:55:53 -03:00
test_context.go Remove most of the time.Sleep from the e2e tests 2018-04-19 17:48:50 -03:00
util.go Adjust default timeout for e2e tests (#3495) 2018-11-30 18:55:53 -03:00