github/kubernetes
1
0
Fork 0
mirror of https://github.com/k3s-io/kubernetes.git synced 2025-09-13 13:14:05 +00:00
Code Issues Projects Releases Wiki Activity

Merge pull request #11352 from JanetKuo/docs-reachable

Browse Source 
Ensure all docs and examples in user guide are reachable
This commit is contained in:
Brian Grant
2015-07-16 23:33:45 -07:00
parent 1ee86d05cb b0c68c4b81
commit 5f34630aca
29 changed files with 75 additions and 45 deletions
Download Patch File Download Diff File Expand all files Collapse all files

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

@@ -241,7 +241,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”](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. See the [rolling update design document](../design/simple-rolling-update.md) and the [example of rolling update](update-demo/) for more information.
Let’s say you were running version 1.7.9 of nginx:
```yaml