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
This commit is contained in:
parent
648e016154
commit
3685419042
|
@ -54,6 +54,9 @@ spec:
|
||||||
effect: NoSchedule
|
effect: NoSchedule
|
||||||
- key: CriticalAddonsOnly
|
- key: CriticalAddonsOnly
|
||||||
operator: Exists
|
operator: Exists
|
||||||
|
- key: node.kubernetes.io/not-ready
|
||||||
|
operator: Exists
|
||||||
|
effect: NoSchedule
|
||||||
terminationGracePeriodSeconds: {{ .Values.pod.lifecycle.termination_grace_period.daemonset_anchor.timeout }}
|
terminationGracePeriodSeconds: {{ .Values.pod.lifecycle.termination_grace_period.daemonset_anchor.timeout }}
|
||||||
containers:
|
containers:
|
||||||
- name: etcdctl
|
- name: etcdctl
|
||||||
|
|
|
@ -52,6 +52,9 @@ spec:
|
||||||
- key: node.kubernetes.io/network-unavailable
|
- key: node.kubernetes.io/network-unavailable
|
||||||
effect: NoSchedule
|
effect: NoSchedule
|
||||||
operator: Exists
|
operator: Exists
|
||||||
|
- key: node.kubernetes.io/not-ready
|
||||||
|
operator: Exists
|
||||||
|
effect: NoSchedule
|
||||||
containers:
|
containers:
|
||||||
- name: "{{ .Release.Name }}-etcd-test"
|
- name: "{{ .Release.Name }}-etcd-test"
|
||||||
env:
|
env:
|
||||||
|
|
|
@ -46,6 +46,9 @@ spec:
|
||||||
effect: NoSchedule
|
effect: NoSchedule
|
||||||
- key: CriticalAddonsOnly
|
- key: CriticalAddonsOnly
|
||||||
operator: Exists
|
operator: Exists
|
||||||
|
- key: node.kubernetes.io/not-ready
|
||||||
|
operator: Exists
|
||||||
|
effect: NoSchedule
|
||||||
containers:
|
containers:
|
||||||
- name: proxy
|
- name: proxy
|
||||||
image: {{ .Values.images.tags.proxy }}
|
image: {{ .Values.images.tags.proxy }}
|
||||||
|
|
Loading…
Reference in New Issue