8cc31b648e
Automatic merge from submit-queue Run CI Jenkins node e2e tests in project k8s-jkns-ci-node-e2e Fixes #27648. If node VMs leak, they should only harm themselves, not the rest of Jenkins. This also lets us do VM cleanup without worrying that we might accidentally delete important Jenkins VMs. The `k8s-jkns-ci-node-e2e` should have the right ACLs in place already. The quota is at defaults, but I don't think we'll need to increase it at this point. |
||
|---|---|---|
| .. | ||
| environment | ||
| jenkins | ||
| runner | ||
| cgroup_manager_test.go | ||
| container_manager_test.go | ||
| container.go | ||
| density_test.go | ||
| disk_eviction_test.go | ||
| doc.go | ||
| e2e_build.go | ||
| e2e_node_suite_test.go | ||
| e2e_remote.go | ||
| e2e_service.go | ||
| image_conformance_test.go | ||
| image_list.go | ||
| image.go | ||
| kubelet_test.go | ||
| memory_eviction_test.go | ||
| mirror_pod_test.go | ||
| OWNERS | ||
| README.md | ||
| resource_collector.go | ||
| resource_usage_test.go | ||
| runtime_conformance_test.go | ||
| util.go | ||
PLEASE NOTE: This document applies to the HEAD of the source tree
If you are using a released version of Kubernetes, you should refer to the docs that go with that version.
The latest release of this document can be found [here](http://releases.k8s.io/release-1.1/docs/devel/collab.md).Documentation for other releases can be found at releases.k8s.io.
See e2e-node-tests