From 95a4a105cd5e626edca2f8f00eb3dff32f1f1c5c Mon Sep 17 00:00:00 2001 From: Christoph Blecker Date: Thu, 21 Dec 2017 17:53:39 -0800 Subject: Use git.k8s.io for links --- contributors/devel/node-performance-testing.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'contributors/devel/node-performance-testing.md') diff --git a/contributors/devel/node-performance-testing.md b/contributors/devel/node-performance-testing.md index 4afa8d25..d43737a8 100644 --- a/contributors/devel/node-performance-testing.md +++ b/contributors/devel/node-performance-testing.md @@ -26,7 +26,7 @@ Heapster will hide the performance cost of serving those stats in the Kubelet. Disabling addons is simple. Just ssh into the Kubernetes master and move the addon from `/etc/kubernetes/addons/` to a backup location. More details -[here](https://github.com/kubernetes/kubernetes/tree/master/cluster/addons/). +[here](https://git.k8s.io/kubernetes/cluster/addons/). ### Which / how many pods? @@ -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/blob/master/test/e2e/node/kubelet_perf.go). To +components: [kubelet_perf.go](https://git.k8s.io/kubernetes/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. -- cgit v1.2.3