From 72e958b394a063e08f3a656a800a732c1dff1cc3 Mon Sep 17 00:00:00 2001 From: Sam Ghods Date: Thu, 26 May 2016 14:31:15 -0700 Subject: [PATCH] Update cluster-management.md --- docs/admin/cluster-management.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/admin/cluster-management.md b/docs/admin/cluster-management.md index 122a376ea3..8e4d394a00 100644 --- a/docs/admin/cluster-management.md +++ b/docs/admin/cluster-management.md @@ -102,7 +102,7 @@ that you have Google Cloud Monitoring API enabled in Google Developer Console. 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 -(5 minutes is the default timeout, controlled by `--pod-eviction-timeout` on the controller-manager), +(the default time is 5 minutes, controlled by `--pod-eviction-timeout` on the controller-manager), then the node controller will terminate the pods that are bound to the unavailable node. If there is a corresponding replica set (or 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, assuming that not all nodes will go down at the same time.