From 8faaf35da036e04ea5a7e66195b2ff3323fc28af Mon Sep 17 00:00:00 2001 From: Bridget Kromhout Date: Mon, 26 Feb 2018 16:48:52 -0600 Subject: [PATCH] Clarify we didn't tag the v1 release --- slides/kube/rollout.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/slides/kube/rollout.md b/slides/kube/rollout.md index 10a49913..21e25898 100644 --- a/slides/kube/rollout.md +++ b/slides/kube/rollout.md @@ -149,7 +149,7 @@ Our rollout is stuck. However, the app is not dead (just 10% slower). - We want to: - - revert to `v0.1` + - revert to `v0.1` (which we now realize we didn't tag - yikes!) - be conservative on availability (always have desired number of available workers) - be aggressive on rollout speed (update more than one pod at a time) - give some time to our workers to "warm up" before starting more @@ -163,7 +163,7 @@ spec: spec: containers: - name: worker - image: $REGISTRY/worker:v0.1 + image: $REGISTRY/worker:latest strategy: rollingUpdate: maxUnavailable: 0 @@ -192,7 +192,7 @@ spec: spec: containers: - name: worker - image: $REGISTRY/worker:v0.1 + image: $REGISTRY/worker:latest strategy: rollingUpdate: maxUnavailable: 0