github
/
k3s
mirror of https://github.com/k3s-io/k3s
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
k3s/test/e2e/node
History
Kubernetes Submit Queue 06bac1880d
Merge pull request #67108 from yujuhong/crictl-test 
Automatic merge from submit-queue. If you want to cherry-pick this change to another branch, please follow the instructions <a href="https://github.com/kubernetes/community/blob/master/contributors/devel/cherry-picks.md">here</a>.

GCE: add a crictl test

This verifies that crictl is available on the node.



**What this PR does / why we need it**:

**Which issue(s) this PR fixes** *(optional, in `fixes #<issue number>(, fixes #<issue_number>, ...)` format, will close the issue(s) when PR gets merged)*:
Fixes #

**Special notes for your reviewer**:

**Release note**:

```release-note
NONE
```
 		2018-08-08 13:22:17 -07:00
..
BUILD GCE: add a crictl test 2018-08-08 10:25:17 -07:00
OWNERS move sig-node related e2e tests to node subdir 2017-07-25 15:22:43 -07:00
README.md Add a README in test/e2e/node with a warning 2018-07-06 16:48:35 -07:00
apparmor.go enable to specific unconfined AppArmor profile 2017-09-28 10:06:36 +08:00
crictl.go GCE: add a crictl test 2018-08-08 10:25:17 -07:00
events.go Adding details to Conformance Tests using RFC 2119 standards. 2018-07-31 17:21:18 -07:00
framework.go Rename e2e sig framework files 2017-08-02 09:33:19 +08:00
kubelet.go e2e test harness - use busybox from dockerhub 2018-08-07 11:22:16 -04:00
kubelet_perf.go Remove kubectl reapers 2018-05-25 22:18:05 +02:00
mount_propagation.go e2e test harness - use busybox from dockerhub 2018-08-07 11:22:16 -04:00
pod_gc.go e2e test harness - use busybox from dockerhub 2018-08-07 11:22:16 -04:00
pods.go Update the nginx image from hub.docker.com 2018-08-04 05:19:53 +05:30
pre_stop.go e2e test harness - use busybox from dockerhub 2018-08-07 11:22:16 -04:00
security_context.go e2e test harness - use busybox from dockerhub 2018-08-07 11:22:16 -04:00
ssh.go migration pod relevant e2e tests to sig node 2017-11-07 11:16:59 +08: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.