Set hard memory eviction thresholds for GCE clusters.

Signed-off-by: Vishnu kannan <vishnuk@google.com>

Author: vishh

cluster/gce/config-default.sh

@@ -138,3 +138,6 @@ OPENCONTRAIL_PUBLIC_SUBNET="${OPENCONTRAIL_PUBLIC_SUBNET:-10.1.0.0/16}"
 HAIRPIN_MODE="${HAIRPIN_MODE:-promiscuous-bridge}" # promiscuous-bridge, hairpin-veth, none
 # Optional: if set to true, kube-up will configure the cluster to run e2e tests.
 E2E_STORAGE_TEST_ENVIRONMENT=${KUBE_E2E_STORAGE_TEST_ENVIRONMENT:-false}
+
+# Evict pods whenever compute resource availability on the nodes gets below a threshold.
+EVICTION_HARD="${EVICTION_HARD:-memory.available<100Mi}"

cluster/gce/config-test.sh

@@ -170,3 +170,6 @@ E2E_STORAGE_TEST_ENVIRONMENT=${KUBE_E2E_STORAGE_TEST_ENVIRONMENT:-false}
 # Optional: if set to true, a image puller is deployed. Only for use in e2e clusters.
 # TODO: Pipe this through GKE e2e clusters once we know it helps.
 PREPULL_E2E_IMAGES="${PREPULL_E2E_IMAGES:-true}"
+
+# Evict pods whenever compute resource availability on the nodes gets below a threshold.
+EVICTION_HARD="${EVICTION_HARD:-memory.available<100Mi}"