k3s/test/e2e/node
Kubernetes Prow Robot faaec7f997
Merge pull request #75177 from mm4tt/node-problem-detector
Disable NodeProblemDector test in large clusters.
2019-03-09 11:31:29 -08:00
..
BUILD Migrate to internal node.k8s.io client 2019-03-07 11:57:12 -08:00
OWNERS Updated OWNERS files to include link to docs 2019-02-04 22:33:12 +01:00
README.md Update deprecated links 2019-02-15 09:13:07 -05:00
apparmor.go enable to specific unconfined AppArmor profile 2017-09-28 10:06:36 +08:00
crictl.go GCE: add a crictl test 2018-08-08 10:25:17 -07:00
events.go Merge pull request #66209 from tianshapjq/should-not-fmtprintf 2018-08-17 02:27:10 -07:00
framework.go Rename e2e sig framework files 2017-08-02 09:33:19 +08:00
kubelet.go e2e test harness - use busybox from dockerhub 2018-08-07 11:22:16 -04:00
kubelet_perf.go Remove e2e-image-puller 2018-09-03 20:43:54 -04:00
mount_propagation.go e2e test harness - use busybox from dockerhub 2018-08-07 11:22:16 -04:00
node_problem_detector.go Merge pull request #75177 from mm4tt/node-problem-detector 2019-03-09 11:31:29 -08:00
pod_gc.go e2e test harness - use busybox from dockerhub 2018-08-07 11:22:16 -04:00
pods.go removed flaky watch from pods test cases 2019-02-27 11:24:20 +05:30
pre_stop.go graceful pod termination with preStop container lifecycle hook 2019-01-17 14:51:37 +05:30
runtimeclass.go Update tests for RuntimeClass beta 2019-03-08 13:21:52 -08:00
security_context.go Promote RunAsGroup to Beta 2019-02-28 17:24:39 -08:00
ssh.go e2e: change test strings to avoid error highlighting 2018-10-03 09:37:26 -07:00
ttlafterfinished.go Report proper namespace in TTLAfterFinished test 2019-01-22 15:42:41 +01: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.