Commit 8db2677e authored by Derek Parker's avatar Derek Parker

docs: Update proposal to address node draining

parent 73973b42
...@@ -128,6 +128,10 @@ services](https://github.com/kubernetes/kubernetes/issues/5754). ...@@ -128,6 +128,10 @@ services](https://github.com/kubernetes/kubernetes/issues/5754).
persist the configuration for bootstrap kubelet on the node. Once we have persist the configuration for bootstrap kubelet on the node. Once we have
checkpointing in kubelet, we will checkpoint the updated config and have the checkpointing in kubelet, we will checkpoint the updated config and have the
bootstrap kubelet use the updated config, if it were to take over. 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 ## Other discussion
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment