From 7b3946776c049f8ffea0b74fefcf03eb95e706fd Mon Sep 17 00:00:00 2001
From: Cezary Zawadka <czawadka@google.com>
Date: Wed, 19 Dec 2018 21:00:22 +0100
Subject: [PATCH] Update scaler-deployment.yaml CPU_LIMITS

setting CPU_LIMITS to '1' fixes the following log appearing every 60 seconds:
Running: kubectl set resources -n kube-system ds fluentd-gcp-v3.1.0 -c fluentd-gcp --requests=cpu=100m,memory=200Mi --limits=cpu=1000m,memory=500Mi
error: info: {extensions v1beta1 daemonsets} "fluentd-gcp-v3.1.0" was not changed

this PR does not change scaler's behaviour, pods are scaled correctly despite error in the logs
---
 cluster/addons/fluentd-gcp/scaler-deployment.yaml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/cluster/addons/fluentd-gcp/scaler-deployment.yaml b/cluster/addons/fluentd-gcp/scaler-deployment.yaml
index 04e0e31b827..6023709ba18 100644
--- a/cluster/addons/fluentd-gcp/scaler-deployment.yaml
+++ b/cluster/addons/fluentd-gcp/scaler-deployment.yaml
@@ -31,6 +31,6 @@ spec:
         - name: MEMORY_REQUEST
           value: 200Mi
         - name: CPU_LIMIT
-          value: 1000m
+          value: '1'
         - name: MEMORY_LIMIT
           value: 500Mi