From 6ea8780ec75691200909dae4368157235ad0f3c3 Mon Sep 17 00:00:00 2001 From: Mark Bishop Date: Fri, 21 Sep 2018 16:25:48 -0700 Subject: [PATCH] added note about k8s known issue --- content/rancher/v2.x/en/k8s-in-rancher/nodes/_index.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/content/rancher/v2.x/en/k8s-in-rancher/nodes/_index.md b/content/rancher/v2.x/en/k8s-in-rancher/nodes/_index.md index 97235255e25..2dc2d9b142b 100644 --- a/content/rancher/v2.x/en/k8s-in-rancher/nodes/_index.md +++ b/content/rancher/v2.x/en/k8s-in-rancher/nodes/_index.md @@ -69,7 +69,9 @@ The following list describes each drain option: - **Timeout** - The amount of time drain should continue to wait before giving up. + The amount of time drain should continue to wait before giving up. + + >**Kubernetes Known Issue:** Currently, the [timeout setting](https://github.com/kubernetes/kubernetes/pull/64378) is not enforced while draining a node. This issue will be corrected as of Kubernetes 1.12. If there's any error related to user input, the node enters a `cordoned` state because the drain failed. You can either correct the input and attempt to drain the node again, or you can abort by uncordoning the node.