github
/
k3s
mirror of https://github.com/k3s-io/k3s
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

Fix failing density test in 100-node clusters

pull/6/head
Wojciech Tyczynski 2017-02-06 12:18:10 +01:00
parent 1df1ad9d34
commit e3c098442d
1 changed files with 7 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
test/e2e/density.go
View File

@ -143,8 +143,13 @@ func density30AddonResourceVerifier(numNodes int) map[string]framework.ResourceC
MemoryConstraint: 100 * (1024 * 1024), MemoryConstraint: 100 * (1024 * 1024),
} }
constraints["kube-proxy"] = framework.ResourceConstraint{ constraints["kube-proxy"] = framework.ResourceConstraint{
CPUConstraint: 0.15, CPUConstraint: 0.15,
MemoryConstraint: 30 * (1024 * 1024), // When we are running purely density test, 30MB seems to be enough.
// However, we are usually running Density together with Load test.
// Thus, if Density is running after Load (which is creating and
// propagating a bunch of services), kubeproxy is using much more
// memory and not releasing it afterwards.
MemoryConstraint: 60 * (1024 * 1024),
} }
constraints["l7-lb-controller"] = framework.ResourceConstraint{ constraints["l7-lb-controller"] = framework.ResourceConstraint{
CPUConstraint: 0.15, CPUConstraint: 0.15,