Parametrize latency pod cpu and memory requests in load test

clusterloader2/testing/load/config.yaml

@@ -21,6 +21,13 @@
 {{$ENABLE_NETWORKPOLICIES := DefaultParam .CL2_ENABLE_NETWORKPOLICIES false}}
 {{$ENABLE_DNSTESTS := DefaultParam .CL2_ENABLE_DNSTESTS false}}
 {{$ENABLE_DENSITY_TEST := DefaultParam .CL2_ENABLE_DENSITY_TEST false}}
+# LATENCY_POD_MEMORY and LATENCY_POD_CPU are calculated for 1-core 4GB node.
+# Increasing allocation of both memory and cpu by 10%
+# decreases the value of priority function in scheduler by one point.
+# This results in decreased probability of choosing the same node again.
+# TODO(https://github.com/kubernetes/perf-tests/issues/1024): See whether we can get rid of this
+{{$LATENCY_POD_CPU := DefaultParam .CL2_LATENCY_POD_CPU 100}}
+{{$LATENCY_POD_MEMORY := DefaultParam .CL2_LATENCY_POD_MEMORY 350}}
 {{$ENABLE_SYSTEM_POD_METRICS:= DefaultParam .ENABLE_SYSTEM_POD_METRICS true}}
 {{$ENABLE_CLUSTER_OOMS_TRACKER := DefaultParam .CL2_ENABLE_CLUSTER_OOMS_TRACKER true}}
 {{$CLUSTER_OOMS_IGNORED_PROCESSES := DefaultParam .CL2_CLUSTER_OOMS_IGNORED_PROCESSES ""}}
@@ -504,13 +511,8 @@ steps:
       templateFillMap:
         Replicas: 1
         Group: latency
-        # CPU and memory requests are calculated for 1-core 4GB node.
-        # Increasing allocation of both memory and cpu by 10% decreases the
-        # value of priority function in scheduler by one point.
-        # This results in decreased probability of choosing the same node again.
-        # TODO(https://github.com/kubernetes/perf-tests/issues/1024): See whether we can get rid of this
-        CpuRequest: 100m
-        MemoryRequest: 350M
+        CpuRequest: {{$LATENCY_POD_CPU}}m
+        MemoryRequest: {{$LATENCY_POD_MEMORY}}M
 - name: Waiting for latency pods to be running
   measurements:
   - Identifier: WaitForRunningLatencyDeployments