kubernetes
/
kops
mirror of https://github.com/kubernetes/kops.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Mark calico-node pods as critical 

When system is low on resources, it is possible that calico-node will be
evicted by kubernetes. That's what happened today in our cluster
bringing down all containers.
This commit is contained in:
Andrey Chernih 2017-05-17 14:52:38 -07:00
parent 511cecfd41
commit c7168937a3
2 changed files with 7 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
upup/models/cloudup/resources/addons/networking.projectcalico.org/k8s-1.6.yaml.template
View File

@ -70,6 +70,8 @@ spec:
labels: labels:
k8s-app: calico-node k8s-app: calico-node
role.kubernetes.io/networking: "1" role.kubernetes.io/networking: "1"
annotations:
scheduler.alpha.kubernetes.io/critical-pod: ''
spec: spec:
hostNetwork: true hostNetwork: true
serviceAccountName: calico serviceAccountName: calico

5
upup/models/cloudup/resources/addons/networking.projectcalico.org/pre-k8s-1.6.yaml.template
View File

@ -70,6 +70,11 @@ spec:
labels: labels:
k8s-app: calico-node k8s-app: calico-node
role.kubernetes.io/networking: "1" role.kubernetes.io/networking: "1"
annotations:
scheduler.alpha.kubernetes.io/critical-pod: ''
scheduler.alpha.kubernetes.io/tolerations: |
[{"key": "dedicated", "value": "master", "effect": "NoSchedule" },
{"key":"CriticalAddonsOnly", "operator":"Exists"}]
spec: spec:
hostNetwork: true hostNetwork: true
containers: containers: