From 8db2677e9ed96d223608690b698a95dc00f31741 Mon Sep 17 00:00:00 2001 From: Derek Parker Date: Wed, 20 Apr 2016 17:12:50 -0700 Subject: [PATCH] docs: Update proposal to address node draining --- docs/proposals/self-hosted-kubelet.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/docs/proposals/self-hosted-kubelet.md b/docs/proposals/self-hosted-kubelet.md index 3ac32d95ff..e5459c2476 100644 --- a/docs/proposals/self-hosted-kubelet.md +++ b/docs/proposals/self-hosted-kubelet.md @@ -128,6 +128,10 @@ services](https://github.com/kubernetes/kubernetes/issues/5754). persist the configuration for bootstrap kubelet on the node. Once we have checkpointing in kubelet, we will checkpoint the updated config and have the bootstrap kubelet use the updated config, if it were to take over. +* Currently best practice when upgrading the kubelet on a node is to drain all + pods first. Automatically draining of the node during kubelet upgrade is out + of scope for this proposal. It is assumed that either the cluster + administrator or the daemonset upgrade policy will handle this. ## Other discussion