kubernetes/test/e2e/node
Yuan Wang 906134cee9 Update pod after the container is removed
Ensures the single-container pod can restart quickly
2026-03-05 23:21:33 +00:00
..
apparmor.go
crictl.go Revert "Add retries to node's crictl test" 2025-09-08 20:35:31 -04:00
events.go E2E: remove unnecessary trailing spaces in test names 2026-01-07 12:05:43 +01:00
examples.go
framework.go
gpu.go test/e2e/node: handle quick pod completion in GPU startup wait 2026-03-01 11:50:57 -08:00
kubelet.go Remove redundant re-assignments in for-loops in test/{e2e,integration,utils} 2026-01-25 22:58:27 +01:00
kubelet_authz.go Merge pull request #131409 from bertinatto/fix-authz-test 2025-05-08 14:39:15 -07:00
kubelet_perf.go
mount_propagation.go fix: Fix non-constant format string in framework.Logf call 2025-04-22 14:01:41 +08:00
node_lifecycle.go feat: Add matcher and conformance tests ensuring that RV is uint128 2025-10-01 00:01:50 +00:00
node_problem_detector.go deprecate nodefeature for feature labels 2025-01-20 17:02:59 -05:00
OWNERS Add ffromani as approver for kubelet resource managers and their tests 2025-01-14 13:18:40 +01:00
pod_admission.go merging the pod rejection 2026-03-03 13:58:04 -05:00
pod_gc.go
pod_resize.go Move getNodeAllocatableAndAvailableValues to framework 2026-01-21 19:41:08 +01:00
pods.go Update pod after the container is removed 2026-03-05 23:21:33 +00:00
pre_stop.go
README.md
runtimeclass.go E2E: remove unnecessary trailing spaces in test names 2026-01-07 12:05:43 +01:00
security_context.go e2e test cases should support seccomp default, which is unconfined [LinuxOnly]. Execution failed. 2026-02-11 08:17:31 +08:00
ssh.go
taints.go fix: enable and fixes rules from testifylint on test package 2024-06-30 05:44:47 +00:00

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.