From 0305c3783f21806bb5d23c6b3bda4c56bf3f0443 Mon Sep 17 00:00:00 2001 From: Bridget Kromhout Date: Mon, 23 Apr 2018 10:52:29 -0500 Subject: [PATCH] Adding an overview; marking clarification as extra --- slides/kube/rollout.md | 16 +++++++++++++++- 1 file changed, 15 insertions(+), 1 deletion(-) diff --git a/slides/kube/rollout.md b/slides/kube/rollout.md index 8aa7df09..a6120b9f 100644 --- a/slides/kube/rollout.md +++ b/slides/kube/rollout.md @@ -158,7 +158,21 @@ Our rollout is stuck. However, the app is not dead (just 10% slower). --- -## Why 10% slower? +## What's going on with our rollout? + +- Why is our app 10% slower? + +- Because `MaxUnavailable=1`, so the rollout terminated 1 replica out of 10 available + +- Okay, but why do we see 2 new replicas being rolled out? + +- Because `MaxSurge=1`, so in addition to replacing the terminated one, the rollout is also starting one more + +--- + +class: extra-details + +## The nitty-gritty details - We start with 10 pods running for the `worker` deployment