Merge pull request #4955 from adisky/fix-doc

estesp · web-flow · commit c35b4cfed520 · 2021-01-20T08:46:17.000-05:00
Clean Up Doc and fix some broken links
diff --git a/README.md b/README.md
@@ -283,7 +283,6 @@ See results on the containerd k8s [test dashboard](https://k8s-testgrid.appspot.
 A Kubernetes incubator project, [cri-tools](https://github.com/kubernetes-sigs/cri-tools), includes programs for exercising CRI implementations. More importantly, cri-tools includes the program `critest` which is used for running [CRI Validation Testing](https://github.com/kubernetes/community/blob/master/contributors/devel/sig-node/cri-validation.md).
 
 #### CRI Guides
-* [Bringing up a Production Quality Cluster on GCE](docs/cri/kube-up.md)
 * [Installing with Ansible and Kubeadm](contrib/ansible/README.md)
 * [For Non-Ansible Users, Preforming a Custom Installation Using the Release Tarball and Kubeadm](docs/cri/installation.md)
 * [CRI Plugin Testing Guide](./docs/cri/testing.md)
diff --git a/docs/cri/installation.md b/docs/cri/installation.md
@@ -129,4 +129,4 @@ systemctl daemon-reload
 ## Bring Up the Cluster
 Now you should have properly installed all required binaries and dependencies on each of your node.
 
-The next step is to use kubeadm to bring up the Kubernetes cluster. It is the same with [the ansible installer](../contrib/ansible). Please follow the steps 2-4 [here](../contrib/ansible/README.md#step-2).
+The next step is to use kubeadm to bring up the Kubernetes cluster. It is the same with [the ansible installer](../../contrib/ansible). Please follow the steps 2-4 [here](../../contrib/ansible/README.md#step-2).
diff --git a/docs/cri/kube-up.md b/docs/cri/kube-up.md
diff --git a/docs/cri/testing.md b/docs/cri/testing.md
@@ -25,10 +25,10 @@ containerd -l debug
 
 [More information](https://github.com/kubernetes-sigs/cri-tools) about CRI validation test.
 ## Node E2E Test
-[Node e2e test](https://github.com/kubernetes/community/blob/master/contributors/devel/e2e-node-tests.md) is a test framework testing Kubernetes node level functionalities such as managing pods, mounting volumes etc. It starts a local cluster with Kubelet and a few other minimum dependencies, and runs node functionality tests against the local cluster.
+[Node e2e test](https://github.com/kubernetes/community/blob/master/contributors/devel/sig-node/e2e-node-tests.md) is a test framework testing Kubernetes node level functionalities such as managing pods, mounting volumes etc. It starts a local cluster with Kubelet and a few other minimum dependencies, and runs node functionality tests against the local cluster.
 
 Currently e2e-node tests are supported from via Pull Request comments on github.
 Enter "/test all" as a comment on a pull request for a list of testing options that have been integrated through prow bot with kubernetes testing services hosted on GCE.
 Typing `/test pull-containerd-node-e2e` will start a node e2e test run on your pull request commits.
 
-[More information](https://github.com/kubernetes/community/blob/master/contributors/devel/e2e-node-tests.md) about Kubernetes node e2e test.
+[More information](https://github.com/kubernetes/community/blob/master/contributors/devel/sig-node/e2e-node-tests.md) about Kubernetes node e2e test.
