diff --git a/test/e2e/density.go b/test/e2e/density.go
index d9d3c6fb81b..811f7d9bff6 100644
--- a/test/e2e/density.go
+++ b/test/e2e/density.go
@@ -143,8 +143,13 @@ func density30AddonResourceVerifier(numNodes int) map[string]framework.ResourceC
 		MemoryConstraint: 100 * (1024 * 1024),
 	}
 	constraints["kube-proxy"] = framework.ResourceConstraint{
-		CPUConstraint:    0.15,
-		MemoryConstraint: 30 * (1024 * 1024),
+		CPUConstraint: 0.15,
+		// 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{
 		CPUConstraint:    0.15,