diff options
| author | XsWack <xushiwei5@huawei.com> | 2017-08-22 10:54:53 +0800 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2017-08-22 10:54:53 +0800 |
| commit | 2d1429ecacab37af056184d4e2197edf4a6d26be (patch) | |
| tree | a4d586f82ea9daa820f7901c401afd1e626a869a | |
| parent | d2bcc0baf97a23f517368b2b0ba48cb3876fcbdf (diff) | |
Update node-performance-testing.md
fix bad url
| -rw-r--r-- | contributors/devel/node-performance-testing.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/contributors/devel/node-performance-testing.md b/contributors/devel/node-performance-testing.md index 4e9e7c1a..f156beec 100644 --- a/contributors/devel/node-performance-testing.md +++ b/contributors/devel/node-performance-testing.md @@ -57,7 +57,7 @@ sampling. ## E2E Performance Test There is an end-to-end test for collecting overall resource usage of node -components: [kubelet_perf.go](https://github.com/kubernetes/kubernetes/tree/master/test/e2e/kubelet_perf.go). To +components: [kubelet_perf.go](https://github.com/kubernetes/kubernetes/blob/master/test/e2e/node/kubelet_perf.go). To run the test, simply make sure you have an e2e cluster running (`go run hack/e2e.go -- -up`) and [set up](#cluster-set-up) correctly. |