Add not-ready tolerations to kuryr pods

Seems like Kubernetes 1.16 is more strict regarding not-ready taint on
the node and keeps it until CNI is correctly configured. This means that
we at least need kuryr-cni to have toleration for that. This commit adds
it to both kuryr-cni and kuryr-controller as well as missing master
toleration to kuryr-controller.

Change-Id: Ifa9c27a416c3347441a2568b37e1bb7b0eba2f28
This commit is contained in:
Michał Dulko 2019-10-15 14:21:32 +02:00
parent f3a675d40b
commit 9c9eac0c80
1 changed files with 10 additions and 0 deletions

View File

@ -570,6 +570,13 @@ EOF
secret:
secretName: kuryr-certificates
restartPolicy: Always
tolerations:
- key: "node-role.kubernetes.io/master"
operator: "Exists"
effect: "NoSchedule"
- key: "node.kubernetes.io/not-ready"
operator: "Exists"
effect: "NoSchedule"
EOF
}
@ -604,6 +611,9 @@ spec:
- key: node-role.kubernetes.io/master
operator: Exists
effect: NoSchedule
- key: "node.kubernetes.io/not-ready"
operator: "Exists"
effect: "NoSchedule"
serviceAccountName: kuryr-controller
containers:
- name: kuryr-cni