Files

tanjunchen bed22fbb44 WaitForPodReady is simply wrapper functions for e2epod package,

and they made an invalid dependency to sub e2e framework from the core framework.

So we can use e2epod.WaitTimeoutForPodReadyInNamespace to remove invalid dependency.

The main purpose of this pr is to handle the framework core package dependency subpackage pod.

2020-03-22 23:08:52 +08:00

apparmor.go

e2e/node/:Use e2eskipper package

2020-01-10 16:21:12 +08:00

BUILD

Test that an always-fail container can't report the pod Succeeded

2020-03-04 13:34:20 -05:00

crictl.go

e2e/node/:Use e2eskipper package

2020-01-10 16:21:12 +08:00

events.go

Use e2epod.WaitForPodNameRunningInNamespace directly

2020-03-17 00:13:14 +00: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

WaitForPodReady is simply wrapper functions for e2epod package,

2020-03-22 23:08:52 +08: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

Use e2epod.WaitForPodNameRunningInNamespace directly

2020-03-17 00:13:14 +00:00

pre_stop.go

Use e2epod.WaitForPodNameRunningInNamespace directly

2020-03-17 00:13:14 +00: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

Use e2epod.WaitForPodNameRunningInNamespace directly

2020-03-17 00:13:14 +00:00

ssh.go

e2e/node/:Use e2eskipper package

2020-01-10 16:21:12 +08:00

taints.go

cleanup: move the test of TaintBasedEvictions features to sig-node

2020-03-04 10:28:00 +09: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.