whentimeslows/website
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

clarify rollout behavior in deployment

Browse Source
This commit is contained in:
chenxuc
2021-07-10 22:01:56 +08:00
parent d7da6f8af8
commit 1955629f42
1 changed files with 2 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
content/en/docs/concepts/workloads/controllers/deployment.md
+2 -1
View File
@@ -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. apply multiple fixes in between pausing and resuming without triggering unnecessary rollouts.
* For example, with a Deployment that was created: * For example, with a Deployment that was created:
Get the Deployment details: Get the Deployment details:
```shell ```shell
kubectl get deploy kubectl get deploy
@@ -759,7 +760,7 @@ apply multiple fixes in between pausing and resuming without triggering unnecess
REVISION CHANGE-CAUSE REVISION CHANGE-CAUSE
1 <none> 1 <none>
``` ```
* 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 ```shell
kubectl get rs kubectl get rs
``` ```