kubernetes/test/e2e
Filipe Brandenburger e9591382a7 Use a custom namespace for running liveness e2e test cases.
This will allow us greated isolation between test case runs without the
need to include randomized uuids to many of the fields in the pods,
services and rcs creation requests.

Tested:
- Ran two instances of `e2e -t TestLivenessHttp -t TestLivenessExec`
  simultaneously and confirmed that pod names did not clash and that
  both of them completed successfully.
2015-02-04 16:05:54 -08:00
..
basic.go Initial adoption of ginkgo in e2e tests 2015-01-28 15:09:53 -08:00
cluster_dns.go Reenable TestClusterDNS on GKE now that 0.9.2 is default 2015-02-04 09:34:40 -08:00
driver.go Increase timeout for Go tests 2015-01-30 08:30:26 -08:00
important_urls.go Initial adoption of ginkgo in e2e tests 2015-01-28 15:09:53 -08:00
kubelet_sends_events.go Convert load of test/e2e/pod.json into native Go definition of the api.Pod 2015-01-30 13:21:09 -08:00
liveness.go Use a custom namespace for running liveness e2e test cases. 2015-02-04 16:05:54 -08:00
network.go Fix contrib webserver so that it compiles. 2015-02-02 15:20:28 -08:00
pods.go Merge pull request #4004 from filbranden/e2e_podsvcenv_remove_embedded_json 2015-02-04 14:49:24 -08:00
private.go Add aws to some e2e tests 2015-01-29 20:35:35 -05:00
roservice.go Initial adoption of ginkgo in e2e tests 2015-01-28 15:09:53 -08:00
util.go Use a custom namespace for running liveness e2e test cases. 2015-02-04 16:05:54 -08:00