diff options
| author | Derek Parker <derek.parker@coreos.com> | 2016-04-20 17:12:50 -0700 |
|---|---|---|
| committer | Derek Parker <derek.parker@coreos.com> | 2016-05-02 11:49:43 -0700 |
| commit | e74915941d7e94ee6da227b67dbf87d74c18af03 (patch) | |
| tree | b5bc3436c05317cae7e5ce655c950ea277967601 | |
| parent | 0c5d11ace71ac9718ec6bcb82fce748fa0c4c627 (diff) | |
docs: Update proposal to address node draining
| -rw-r--r-- | self-hosted-kubelet.md | 4 |
1 files changed, 4 insertions, 0 deletions
diff --git a/self-hosted-kubelet.md b/self-hosted-kubelet.md index 3ac32d95..e5459c24 100644 --- a/self-hosted-kubelet.md +++ b/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 |