Files
kubernetes/test/e2e/node
Clayton Coleman 6d98b0a0f4 Test that an always-fail container can't report the pod Succeeded
The kubelet can race when a pod is deleted and report that a container succeeded
when it instead failed, and thus the pod is reported as succeeded. Create an e2e
test that demonstrates this failure.
2020-03-04 13:34:20 -05:00
..
2020-01-10 16:21:12 +08:00
2020-01-10 16:21:12 +08:00
2020-02-08 12:30:21 -05:00
2019-05-12 07:35:13 +08:00
2020-02-08 12:30:21 -05:00
2019-10-10 15:52:51 -05:00
2020-02-08 12:30:21 -05:00
2020-02-08 12:30:21 -05:00
2019-02-15 09:13:07 -05:00
2020-01-10 16:21:12 +08:00
2020-02-08 12:30:21 -05:00

WARNING: Do not add tests in this directory

There are two types of end-to-end tests in Kubernetes:

Tests located in ${KUBE_ROOT}/test/e2e/common are shared by both Cluster and Node E2E test jobs. Tests in ${KUBE_ROOT}/test/e2e_node are exclusively owned by Node E2E. If you want to add a test, most likely than not, you want to add the test to one of the two directories mentioned above. If you are unsure, please check with the OWNER of the directory. This directory currently contains misplaced and legacy tests; they will be cleaned up in the future.