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

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

View file

@ -45,19 +45,15 @@ spec:
labels:
k8s-app: calico-typha
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'
spec:
nodeSelector:
beta.kubernetes.io/os: linux
hostNetwork: true
tolerations:
# Mark the pod as a critical add-on for rescheduling.
- key: CriticalAddonsOnly
- key: node-role.kubernetes.io/master
operator: Exists
effect: NoSchedule
# Since Calico can't network a pod until Typha is up, we need to run Typha itself
# as a host-networked pod.
serviceAccountName: calico-node