|
1 | 1 | # Container Runtime Interface (CRI) Validation Testing |
2 | 2 |
|
3 | | -CRI validation testing provides a test framework and a suite of tests to validate that the Container Runtime Interface (CRI) server implementation meets all the requirements. This allows the CRI runtime developers to verify that their runtime conforms to CRI, without needing to set up Kubernetes components or run Kubernetes end-to-end tests. |
| 3 | +This page is DEPRECATED and WILL BE REMOVED. |
4 | 4 |
|
5 | | -CRI validation testing is GA since v1.11.0 and is hosted at the [cri-tools](https://github.com/kubernetes-sigs/cri-tools) repository. We encourage the CRI developers to report bugs or help extend the test coverage by adding more tests. |
6 | | - |
7 | | -## Install |
8 | | - |
9 | | -The test suites can be downloaded from cri-tools [release page](https://github.com/kubernetes-sigs/cri-tools/releases): |
10 | | - |
11 | | -```sh |
12 | | -VERSION="v1.11.0" |
13 | | -wget https://github.com/kubernetes-sigs/cri-tools/releases/download/$VERSION/critest-$VERSION-linux-amd64.tar.gz |
14 | | -sudo tar zxvf critest-$VERSION-linux-amd64.tar.gz -C /usr/local/bin |
15 | | -rm -f critest-$VERSION-linux-amd64.tar.gz |
16 | | -``` |
17 | | - |
18 | | -critest requires [ginkgo](https://github.com/onsi/ginkgo) to run parallel tests. It could be installed by |
19 | | - |
20 | | -```sh |
21 | | -go get -u github.com/onsi/ginkgo/ginkgo |
22 | | -``` |
23 | | - |
24 | | -*Note: ensure GO is installed and GOPATH is set before installing ginkgo.* |
25 | | - |
26 | | -## Running tests |
27 | | - |
28 | | -### Prerequisite |
29 | | - |
30 | | -Before running the test, you need to _ensure that the CRI server under test is running and listening on a Unix socket_. Because the validation tests are designed to request changes (e.g., create/delete) to the containers and verify that correct status is reported, it expects to be the only user of the CRI server. Please make sure that 1) there are no existing CRI-managed containers running on the node, and 2) no other processes (e.g., Kubelet) will interfere with the tests. |
31 | | - |
32 | | -### Run |
33 | | - |
34 | | -```sh |
35 | | -critest |
36 | | -``` |
37 | | - |
38 | | -This will |
39 | | - |
40 | | -- Connect to the shim of CRI container runtime |
41 | | -- Run the tests using `ginkgo` |
42 | | -- Output the test results to STDOUT |
43 | | - |
44 | | -critest connects to `unix:///var/run/dockershim.sock` by default. For other runtimes, the endpoint can be set by flags `-runtime-endpoint` and `-image-endpoint`. |
45 | | - |
46 | | -## Additional options |
47 | | - |
48 | | -- `-ginkgo.focus`: Only run the tests that match the regular expression. |
49 | | -- `-image-endpoint`: Set the endpoint of image service. Same with runtime-endpoint if not specified. |
50 | | -- `-runtime-endpoint`: Set the endpoint of runtime service. Default to `unix:///var/run/dockershim.sock`. |
51 | | -- `-ginkgo.skip`: Skip the tests that match the regular expression. |
52 | | -- `-parallel`: The number of parallel test nodes to run (default 1). ginkgo must be installed to run parallel tests. |
53 | | -- `-h`: Show help and all supported options. |
| 5 | +Content of the page was moved to https://github.com/kubernetes-sigs/cri-tools/blob/master/docs/validation.md. |
0 commit comments