github/kubernetes
4
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
eda96bc958
kubernetes/test/e2e/node
History
Kubernetes Prow Robot a847874655
Merge pull request #83792 from liggitt/flake-pre-stop 
Mark 'wait until preStop hook completes the process' flaky
2019-10-11 13:42:38 -07:00
..
apparmor.go clean up test code 2019-09-05 23:44:19 +08:00
BUILD Use pod + nsenter instead of SSH in mount propagation tests 2019-10-01 10:19:25 +02:00
crictl.go clean up test code 2019-09-05 23:44:19 +08:00
events.go clean up test code 2019-09-05 23:44:19 +08:00
framework.go fix golint error in e2e/node 2019-05-12 07:35:13 +08:00
kubelet_perf.go Merge pull request #82291 from danwinship/getnodes 2019-09-25 11:04:43 -07:00
kubelet.go kubelet e2e: run resource monitor only if the actual number of nodes is 2019-10-10 17:02:51 -07:00
mount_propagation.go Use pod + nsenter instead of SSH in mount propagation tests 2019-10-01 10:19:25 +02:00
node_problem_detector.go Address staticcheck failures for test/e2e/node/... 2019-10-09 10:26:11 -04:00
OWNERS Audit of test/* OWNERS files 2019-10-10 15:52:51 -05:00
pod_gc.go Address staticcheck failures for test/e2e/node/... 2019-10-09 10:26:11 -04:00
pods.go clean up test code 2019-09-05 23:44:19 +08:00
pre_stop.go Mark 'wait until preStop hook completes the process' flaky 2019-10-11 13:09:32 -04:00
README.md Update deprecated links 2019-02-15 09:13:07 -05:00
runtimeclass.go tag test that taints a node as disruptive 2019-10-08 18:22:17 -07:00
security_context.go Address staticcheck failures for test/e2e/node/... 2019-10-09 10:26:11 -04:00
ssh.go clean up test code 2019-09-05 23:44:19 +08:00
ttlafterfinished.go clean up test code 2019-09-05 23:44:19 +08:00

README.md

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.