Fixed for hyperkube 1.12

During bootstrap process kubernetes node is not ready due to missed CNI.
It will be installed later but for a few daemonsets it's critical.
They can't start pods and looping in a while.

Workaround is here: add tolerations.

Change-Id: Ib3c361949ea4e452d599aa7a3a2b7827541b7bac

charts/etcd/templates/daemonset-anchor.yaml

@@ -54,6 +54,9 @@ spec:
           effect: NoSchedule
         - key: CriticalAddonsOnly
           operator: Exists
+        - key: node.kubernetes.io/not-ready
+          operator: Exists
+          effect: NoSchedule
       terminationGracePeriodSeconds: {{ .Values.pod.lifecycle.termination_grace_period.daemonset_anchor.timeout }}
       containers:
         - name: etcdctl

charts/etcd/templates/tests/test-etcd-health.yaml

@@ -52,6 +52,9 @@ spec:
     - key: node.kubernetes.io/network-unavailable
       effect: NoSchedule
       operator: Exists
+    - key: node.kubernetes.io/not-ready
+      operator: Exists
+      effect: NoSchedule
   containers:
     - name: "{{ .Release.Name }}-etcd-test"
       env:

charts/proxy/templates/daemonset.yaml

@@ -46,6 +46,9 @@ spec:
           effect: NoSchedule
         - key: CriticalAddonsOnly
           operator: Exists
+        - key: node.kubernetes.io/not-ready
+          operator: Exists
+          effect: NoSchedule
       containers:
       - name: proxy
         image: {{ .Values.images.tags.proxy }}