From 508c55d588a396575973bc3fe1207afd059cd086 Mon Sep 17 00:00:00 2001 From: George Miroshnykov Date: Tue, 27 Sep 2022 13:45:17 +0300 Subject: [PATCH] docs: fix minor mistakes in Migrating to Deployments Signed-off-by: George Miroshnykov --- docs/migrating.md | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/docs/migrating.md b/docs/migrating.md index ee603a2999..62e3494e3d 100644 --- a/docs/migrating.md +++ b/docs/migrating.md @@ -50,11 +50,11 @@ spec: ## Reference Deployment From Rollout -Instead of removing Deployment you can scale-down in to zero and reference from the Rollout resource: +Instead of removing Deployment you can scale it down to zero and reference it from the Rollout resource: 1. Create a Rollout resource. 1. Reference an existing Deployment using `workloadRef` field. -1. Scale-down existing Deployment by changing `replicas` field of an existing Deployment to zero. +1. Scale-down an existing Deployment by changing `replicas` field of an existing Deployment to zero. 1. To perform an update, the change should be made to the Pod template field of the Deployment. Below is an example of a Rollout resource referencing a Deployment. @@ -150,7 +150,8 @@ When converting a Rollout to a Deployment, it involves changing three fields: When a rollout is referencing to a deployment: -1. Scale-up the Deployment by changing `replicas` field of an existing Rollout to zero. -1. Scale-down existing Rollout by changing `replicas` field of an existing Rollout to zero. +1. Scale-up an existing Deployment by changing its `replicas` field to a desired number of pods. +1. Wait for the Deployment pods to become Ready. +1. Scale-down an existing Rollout by changing its `replicas` field to zero. Please refer to [Running Rollout and Deployment side-by-side](#running-rollout-and-deployment-side-by-side) and [Traffic Management During Migration](#traffic-management-during-migration) for caveats.