From 1548e80f100e27473ce844245f1b8bb9e6beac52 Mon Sep 17 00:00:00 2001 From: Matt Braymer-Hayes Date: Wed, 7 Feb 2018 18:00:43 -0800 Subject: [PATCH] Update nodes.md (#7288) Change "introduces" to "introduced" to reflect v1.8 no longer being the latest version. --- docs/concepts/architecture/nodes.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/concepts/architecture/nodes.md b/docs/concepts/architecture/nodes.md index e4938ae3f2..3d3ce4f5f0 100644 --- a/docs/concepts/architecture/nodes.md +++ b/docs/concepts/architecture/nodes.md @@ -74,7 +74,7 @@ the "Terminating" or "Unknown" states. In cases where Kubernetes cannot deduce f permanently left a cluster, the cluster administrator may need to delete the node object by hand. Deleting the node object from Kubernetes causes all the Pod objects running on it to be deleted from the apiserver, freeing up their names. -Version 1.8 introduces an alpha feature that automatically creates +Version 1.8 introduced an alpha feature that automatically creates [taints](/docs/concepts/configuration/taint-and-toleration/) that represent conditions. To enable this behavior, pass an additional feature gate flag `--feature-gates=...,TaintNodesByCondition=true` to the API server, controller manager, and scheduler.