Commit e3c09844 authored by Wojciech Tyczynski's avatar Wojciech Tyczynski

Fix failing density test in 100-node clusters

parent 1df1ad9d
...@@ -143,8 +143,13 @@ func density30AddonResourceVerifier(numNodes int) map[string]framework.ResourceC ...@@ -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,
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment