From 112a6e59283eb98f3ccdd4b1f787d065f63e843a Mon Sep 17 00:00:00 2001 From: Kay Yan Date: Wed, 28 Feb 2018 03:24:45 +0800 Subject: [PATCH] fix-typo-in-daemonset (#7534) --- 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 e2c00863b8..a20f0f8d39 100644 --- a/docs/concepts/workloads/controllers/daemonset.md +++ b/docs/concepts/workloads/controllers/daemonset.md @@ -124,7 +124,7 @@ due to hard-coded behavior of the NodeController rather than due to tolerations) - `node.kubernetes.io/disk-pressure` When the support to critical pods is enabled and the pods in a DaemonSet are -labelled as critical, the Daemon pods are created with an additional +labeled as critical, the Daemon pods are created with an additional `NoSchedule` toleration for the `node.kubernetes.io/out-of-disk` taint. Note that all above `NoSchedule` taints above are created only in version 1.8 or later if the alpha feature `TaintNodesByCondition` is enabled.