From 1955629f4221f86f0463322da047998e02a19b92 Mon Sep 17 00:00:00 2001 From: chenxuc Date: Sat, 10 Jul 2021 22:01:56 +0800 Subject: [PATCH] clarify rollout behavior in deployment --- content/en/docs/concepts/workloads/controllers/deployment.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/content/en/docs/concepts/workloads/controllers/deployment.md b/content/en/docs/concepts/workloads/controllers/deployment.md index 22b95255c5..beea0f19fb 100644 --- a/content/en/docs/concepts/workloads/controllers/deployment.md +++ b/content/en/docs/concepts/workloads/controllers/deployment.md @@ -709,6 +709,7 @@ You can pause a Deployment before triggering one or more updates and then resume apply multiple fixes in between pausing and resuming without triggering unnecessary rollouts. * For example, with a Deployment that was created: + Get the Deployment details: ```shell kubectl get deploy @@ -759,7 +760,7 @@ apply multiple fixes in between pausing and resuming without triggering unnecess REVISION CHANGE-CAUSE 1 ``` -* Get the rollout status to ensure that the Deployment is updated successfully: +* Get the rollout status to verify that the existing ReplicaSet has not changed: ```shell kubectl get rs ```