From 9862888bb2cea51f5d2fae1fd145203a70f10dbb Mon Sep 17 00:00:00 2001
From: Dalton Hubble <dghubble@gmail.com>
Date: Sun, 24 Mar 2019 11:55:56 -0700
Subject: [PATCH] Reduce calico-node CPU request from 250m to 150m

* calico-node uses only a small fraction of its CPU request
(i.e. reservation) even under stress. The unbounded limit
already allows usage to scale favorably in bursty cases
* Motivation: On instance types that skew memory-optimized
(e.g. GCP n1), over-requesting can push the system toward
overcommitment (alerts can be tuned)
* Overcommitment is not necessarily bad, but 250m seems too
generous a minimum given the actual usage
---
 resources/calico/daemonset.yaml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/resources/calico/daemonset.yaml b/resources/calico/daemonset.yaml
index d022197..69c19e1 100644
--- a/resources/calico/daemonset.yaml
+++ b/resources/calico/daemonset.yaml
@@ -128,7 +128,7 @@ spec:
             privileged: true
           resources:
             requests:
-              cpu: 250m
+              cpu: 150m
           livenessProbe:
             httpGet:
               path: /liveness