C12s/c12s-kubespray
3
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

Add toleration for calico-typha on master (#5405)

Browse source 
Change-Id: Iea9a366cf6ccc4d491bfc49c5d2dba6d98f81b69
This commit is contained in:
Matthew Mosesohn 2019-12-05 17:24:32 +03:00 committed by Kubernetes Prow Robot
parent 37df9a10ff
commit 7da2083986
1 changed files with 2 additions and 6 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

8
roles/network_plugin/calico/templates/calico-typha.yml.j2
View file

@ -45,19 +45,15 @@ spec:
labels: labels:
k8s-app: calico-typha k8s-app: calico-typha
annotations: annotations:
# This, along with the CriticalAddonsOnly toleration below, marks the pod as a critical
# add-on, ensuring it gets priority scheduling and that its resources are reserved
# if it ever gets evicted.
scheduler.alpha.kubernetes.io/critical-pod: ''
cluster-autoscaler.kubernetes.io/safe-to-evict: 'true' cluster-autoscaler.kubernetes.io/safe-to-evict: 'true'
spec: spec:
nodeSelector: nodeSelector:
beta.kubernetes.io/os: linux beta.kubernetes.io/os: linux
hostNetwork: true hostNetwork: true
tolerations: tolerations:
# Mark the pod as a critical add-on for rescheduling. - key: node-role.kubernetes.io/master
- key: CriticalAddonsOnly
operator: Exists operator: Exists
effect: NoSchedule
# Since Calico can't network a pod until Typha is up, we need to run Typha itself # Since Calico can't network a pod until Typha is up, we need to run Typha itself
# as a host-networked pod. # as a host-networked pod.
serviceAccountName: calico-node serviceAccountName: calico-node