github
/
k3s
mirror of https://github.com/k3s-io/k3s
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
k3s/test/e2e/node
History
SataQiu 252cabf155 [e2e] test/e2e/framework/volume_util.go -> test/e2e/framework/volume/fixtures.go 2019-04-13 16:58:37 +08:00
..
BUILD [e2e] test/e2e/framework/volume_util.go -> test/e2e/framework/volume/fixtures.go 2019-04-13 16:58:37 +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
…
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
…
kubelet.go [e2e] test/e2e/framework/volume_util.go -> test/e2e/framework/volume/fixtures.go 2019-04-13 16:58:37 +08:00
kubelet_perf.go remove usages of internal clientset in e2e framework 2019-03-28 21:13:40 -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 promote should be submitted and removed e2e test case to conformance 2019-03-19 15:14:54 +05:30
pre_stop.go graceful pod termination with preStop container lifecycle hook 2019-01-17 14:51:37 +05:30
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 refactor: clean up e2e framework job utils 2019-04-12 21:26:33 +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.