diff options
| author | k8s-ci-robot <k8s-ci-robot@users.noreply.github.com> | 2018-09-07 10:01:09 -0700 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2018-09-07 10:01:09 -0700 |
| commit | 939376c00eae23587fcd9927d6fa169c4e142d10 (patch) | |
| tree | be0cde794e936fdb2cd7f521e54a82db13932c6b | |
| parent | 3dc7e3fb1fca3f7f4966c7b7ee93826516b793e9 (diff) | |
| parent | 7647f3051ce6118e35e0a62a69a8b915438a1ce5 (diff) | |
Merge pull request #2646 from feiskyer/cri-tools
Update links of cri-tools
| -rw-r--r-- | contributors/devel/cri-testing-policy.md | 2 | ||||
| -rw-r--r-- | contributors/devel/cri-validation.md | 6 | ||||
| -rw-r--r-- | keps/sig-node/0014-runtime-class.md | 2 |
3 files changed, 5 insertions, 5 deletions
diff --git a/contributors/devel/cri-testing-policy.md b/contributors/devel/cri-testing-policy.md index d41de619..73b48c5e 100644 --- a/contributors/devel/cri-testing-policy.md +++ b/contributors/devel/cri-testing-policy.md @@ -13,7 +13,7 @@ because many features require integration of runtime, OS, or even the cloud provider. A higher-level integration tests provider better signals on vertical stack compatibility to the Kubernetes community. On the other hand, runtime developers are strongly encouraged to run low-level -[CRI validation test suite](https://github.com/kubernetes-incubator/cri-tools/blob/master/docs/validation.md) +[CRI validation test suite](https://github.com/kubernetes-sigs/cri-tools/blob/master/docs/validation.md) for validation as part of their development process. ## Required and optional tests diff --git a/contributors/devel/cri-validation.md b/contributors/devel/cri-validation.md index efb98022..84842c9b 100644 --- a/contributors/devel/cri-validation.md +++ b/contributors/devel/cri-validation.md @@ -2,15 +2,15 @@ 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. -CRI validation testing is GA since v1.11.0 and is hosted at the [cri-tools](https://github.com/kubernetes-incubator/cri-tools) repository. We encourage the CRI developers to report bugs or help extend the test coverage by adding more tests. +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. ## Install -The test suites can be downloaded from cri-tools [release page](https://github.com/kubernetes-incubator/cri-tools/releases): +The test suites can be downloaded from cri-tools [release page](https://github.com/kubernetes-sigs/cri-tools/releases): ```sh VERSION="v1.11.0" -wget https://github.com/kubernetes-incubator/cri-tools/releases/download/$VERSION/critest-$VERSION-linux-amd64.tar.gz +wget https://github.com/kubernetes-sigs/cri-tools/releases/download/$VERSION/critest-$VERSION-linux-amd64.tar.gz sudo tar zxvf critest-$VERSION-linux-amd64.tar.gz -C /usr/local/bin rm -f critest-$VERSION-linux-amd64.tar.gz ``` diff --git a/keps/sig-node/0014-runtime-class.md b/keps/sig-node/0014-runtime-class.md index cf067b5d..0dff017c 100644 --- a/keps/sig-node/0014-runtime-class.md +++ b/keps/sig-node/0014-runtime-class.md @@ -356,7 +356,7 @@ Alpha: - [CRI validation tests][cri-validation] - Kubernetes E2E tests (only validating single runtime handler cases) -[cri-validation]: https://github.com/kubernetes-incubator/cri-tools/blob/master/docs/validation.md +[cri-validation]: https://github.com/kubernetes-sigs/cri-tools/blob/master/docs/validation.md Beta: |