From 77d5f1231504bd143b6bf96845bf0507396b8387 Mon Sep 17 00:00:00 2001 From: John Gardiner Myers Date: Tue, 1 Sep 2020 21:47:05 -0700 Subject: [PATCH] Improve description of detaching instances --- docs/operations/rolling-update.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/docs/operations/rolling-update.md b/docs/operations/rolling-update.md index a02144c1e2682..92206ddabee44 100644 --- a/docs/operations/rolling-update.md +++ b/docs/operations/rolling-update.md @@ -113,7 +113,9 @@ update. Instead of first draining and terminating an instance and then creating it effectively first creates a new instance and then drains and terminates the old one. Surging is implemented by "detaching" instances, making them not count toward the desired -number of instances in the instance group. The detached instances are updated last; +number of instances in the instance group. This causes the cloud provider to create new +instances in order to satisfy the group's desired number. +The detached instances are drained and terminated last; when they are terminated the cloud provider does not replace them. The `maxSurge` is the maximum number of extra instances that can be created during the update.