Skip to content

Commit

Permalink
minor doc modification
Browse files Browse the repository at this point in the history
  • Loading branch information
@you-n-g
you-n-g committed Mar 25, 2015
1 parent 7085a0c commit c2e0f84
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion docs/cluster_management.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -37,7 +37,7 @@ $ _output/go/bin/kube-version-change -i myPod.v1beta1.yaml -o myPod.v1beta3.yaml
If you need to reboot a node (such as for a kernel upgrade, libc upgrade, hardware repair, etc.), and the downtime is
brief, then when the Kubelet restarts, it will attempt to restart the pods scheduled to it. If the reboot takes longer,
then the node controller will terminate the pods that are bound to the unavailable node. If there is a corresponding
replication controller, the a new copy of the pod will be started on a different node. So, in the the case where all
replication controller, then a new copy of the pod will be started on a different node. So, in the case where all
pods are replicated, upgrades can be done without special coordination.

If you want more control over the upgrading process, you may use the following workflow:
Expand Down

0 comments on commit c2e0f84

Please sign in to comment.