github/kubernetes
1
0
Fork 0
mirror of https://github.com/k3s-io/kubernetes.git synced 2026-01-13 11:25:19 +00:00
Code Issues Projects Releases Wiki Activity

Apply mungedocs changes

Browse Source
This commit is contained in:
Daniel Smith
2015-07-13 17:13:09 -07:00
parent 1263a30644
commit 821e08fded
225 changed files with 1229 additions and 149 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
docs/user-guide/managing-deployments.md
View File

@@ -232,7 +232,7 @@ my-nginx-o0ef1 1/1 Running 0 1h
At some point, you’ll eventually need to update your deployed application, typically by specifying a new image or image tag, as in the canary deployment scenario above. `kubectl` supports several update operations, each of which is applicable to different scenarios.
To update a service without an outage, `kubectl` supports what is called [“rolling update”](../../docs/user-guide/kubectl/kubectl_rolling-update.md), which updates one pod at a time, rather than taking down the entire service at the same time.
To update a service without an outage, `kubectl` supports what is called [“rolling update”](kubectl/kubectl_rolling-update.md), which updates one pod at a time, rather than taking down the entire service at the same time.
Let’s say you were running version 1.7.9 of nginx:
```yaml
@@ -389,4 +389,6 @@ replicationcontrollers/my-nginx-v4
```
<!-- BEGIN MUNGE: GENERATED_ANALYTICS -->
[![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/user-guide/managing-deployments.md?pixel)]()
<!-- END MUNGE: GENERATED_ANALYTICS -->