From 04fc9a30b0c4a20a2c79c62b13a2c8aa7bedd274 Mon Sep 17 00:00:00 2001 From: Michal Cwienczek Date: Thu, 12 Oct 2017 01:32:46 +0200 Subject: [PATCH] Updated link to taints and tolerations (#5871) --- docs/concepts/workloads/controllers/daemonset.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/concepts/workloads/controllers/daemonset.md b/docs/concepts/workloads/controllers/daemonset.md index ee4cf4d4097..04310af23cb 100644 --- a/docs/concepts/workloads/controllers/daemonset.md +++ b/docs/concepts/workloads/controllers/daemonset.md @@ -110,7 +110,7 @@ when the Pod is created, so it is ignored by the scheduler). Therefore: - The DaemonSet controller can make Pods even when the scheduler has not been started, which can help cluster bootstrap. -Daemon Pods do respect [taints and tolerations](/docs/concepts/configuration/assign-pod-node/#taints-and-tolerations-beta-feature), +Daemon Pods do respect [taints and tolerations](/docs/concepts/configuration/taint-and-toleration), but they are created with `NoExecute` tolerations for the following taints with no `tolerationSeconds`: - `node.kubernetes.io/not-ready`