github/kubernetes
4
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
Files
e64169d6b51a1bd31947ce75c85ef6aaa9ba5d88
kubernetes/test/e2e/node
History
Eric Ernst e5760015d2 e2e-framework-node: add runtimeclass to dedup code 
Similar functionality is required across e2e tests for RuntimeClass.
Let's create runtimeclass as part of the framework/node package.

Signed-off-by: Eric Ernst <eric.ernst@intel.com>
2020-02-20 15:58:52 -08:00
..
apparmor.go
e2e/node/:Use e2eskipper package
2020-01-10 16:21:12 +08:00
BUILD
e2e-framework-node: add runtimeclass to dedup code
2020-02-20 15:58:52 -08:00
crictl.go
e2e/node/:Use e2eskipper package
2020-01-10 16:21:12 +08:00
events.go
generated: run refactor
2020-02-08 12:30:21 -05:00
framework.go
fix golint error in e2e/node
2019-05-12 07:35:13 +08:00
kubelet_perf.go
e2e: move LogFailedContainers out of e2e test framework util.go
2019-11-15 10:21:26 +08:00
kubelet.go
generated: run refactor
2020-02-08 12:30:21 -05: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
generated: run refactor
2020-02-07 18:16:47 -08:00
OWNERS
Audit of test/* OWNERS files
2019-10-10 15:52:51 -05:00
pod_gc.go
generated: run refactor
2020-02-08 12:30:21 -05:00
pods.go
generated: run refactor
2020-02-07 18:16:47 -08:00
pre_stop.go
generated: run refactor
2020-02-08 12:30:21 -05:00
README.md
Update deprecated links
2019-02-15 09:13:07 -05:00
runtimeclass.go
e2e-framework-node: add runtimeclass to dedup code
2020-02-20 15:58:52 -08:00
security_context.go
test/e2e/node: fix selinux test failure
2020-02-17 09:46:59 -08:00
ssh.go
e2e/node/:Use e2eskipper package
2020-01-10 16:21:12 +08:00
ttlafterfinished.go
generated: run refactor
2020-02-08 12:30:21 -05: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.