mirror of https://github.com/k3s-io/k3s
![]() Automatic merge from submit-queue Mark runtime conformance tests as flaky and not run them in jenkins CI. For #26809 @pwittrock As discussed offline, marking runtime tests as flaky for now. I'm not sure if those tests are required. Testing docker in every Kubernetes PR is un-necessary. These tests can be run periodically in a separate CI. AFAIK, these tests don't seem to exercise any kube features. |
||
---|---|---|
.. | ||
environment | ||
jenkins | ||
runner | ||
OWNERS | ||
README.md | ||
container.go | ||
container_list.go | ||
container_manager_test.go | ||
doc.go | ||
e2e_build.go | ||
e2e_node_suite_test.go | ||
e2e_remote.go | ||
e2e_service.go | ||
exec_util.go | ||
image.go | ||
image_conformance_test.go | ||
kubelet_test.go | ||
mirror_pod_test.go | ||
privileged_test.go | ||
runtime_conformance_test.go | ||
util.go |
README.md
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