From 3d1972054f8a3af5f20668140551a23b9a956eb4 Mon Sep 17 00:00:00 2001 From: Yu-Ju Hong Date: Mon, 1 Feb 2016 10:29:45 -0800 Subject: [PATCH] Adjust the limits in the kubelet resource tracking test The new limits reflect the recent changes in kubelet, and also account for noise better. --- test/e2e/kubelet_perf.go | 16 ++++++++++++---- 1 file changed, 12 insertions(+), 4 deletions(-) diff --git a/test/e2e/kubelet_perf.go b/test/e2e/kubelet_perf.go index f428ee1478f..59fcf242bae 100644 --- a/test/e2e/kubelet_perf.go +++ b/test/e2e/kubelet_perf.go @@ -160,17 +160,25 @@ var _ = Describe("Kubelet [Serial] [Slow]", func() { rm.Stop() }) Describe("regular resource usage tracking", func() { + // We assume that the scheduler will make reasonable scheduling choices + // and assign ~N pods on the node. + // Although we want to track N pods per node, there are N + add-on pods + // in the cluster. The cluster add-on pods can be distributed unevenly + // among the nodes because they are created during the cluster + // initialization. This *noise* is obvious when N is small. We + // deliberately set higher resource usage limits to account for the + // noise. rTests := []resourceTest{ {podsPerNode: 0, limits: containersCPUSummary{ - "/kubelet": {0.50: 0.05, 0.95: 0.15}, - "/docker-daemon": {0.50: 0.03, 0.95: 0.06}, + "/kubelet": {0.50: 0.06, 0.95: 0.08}, + "/docker-daemon": {0.50: 0.05, 0.95: 0.06}, }, }, {podsPerNode: 35, limits: containersCPUSummary{ - "/kubelet": {0.50: 0.15, 0.95: 0.35}, - "/docker-daemon": {0.50: 0.06, 0.95: 0.30}, + "/kubelet": {0.50: 0.12, 0.95: 0.14}, + "/docker-daemon": {0.50: 0.06, 0.95: 0.08}, }, }, }