mirror of
https://github.com/k3s-io/kubernetes.git
synced 2025-09-13 21:25:09 +00:00
Fix failing density test in 100-node clusters
This commit is contained in:
@@ -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,
|
||||||
|
Reference in New Issue
Block a user