![]() The e2e that create/deletes pods rapidly and verifies their status was reporting a very long timing: timings total=12.211347385s t=491ms run=2s execute=450402h8m25s in a few scenarios. Add error checks that clarify when this happens and why. Report p50/75/90/99 latencies on teardown as observed from the test for baseline for future changes. |
||
---|---|---|
.. | ||
apparmor.go | ||
crictl.go | ||
events.go | ||
examples.go | ||
framework.go | ||
kubelet_perf.go | ||
kubelet.go | ||
mount_propagation.go | ||
node_problem_detector.go | ||
OWNERS | ||
pod_gc.go | ||
pods.go | ||
pre_stop.go | ||
README.md | ||
runtimeclass.go | ||
security_context.go | ||
ssh.go | ||
taints.go |
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.