From f7494aff3632744a5ff43d4807facdabfb67b14d Mon Sep 17 00:00:00 2001 From: Xiaoyu Zhang Date: Wed, 29 Mar 2017 04:26:00 +0800 Subject: [PATCH] Fix the urls Fix the urls --- docs/concepts/configuration/overview.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/concepts/configuration/overview.md b/docs/concepts/configuration/overview.md index 499f81affc..bd615aa2bb 100644 --- a/docs/concepts/configuration/overview.md +++ b/docs/concepts/configuration/overview.md @@ -70,12 +70,12 @@ This document is meant to highlight and consolidate in one place configuration b frontend" pods, or all "test" phase components of app "myapp". See the [guestbook](https://github.com/kubernetes/kubernetes/tree/{{page.githubbranch}}/examples/guestbook/) app for an example of this approach. - A service can be made to span multiple deployments, such as is done across [rolling updates](/docs/user-guide/kubectl/kubectl_rolling-update/), by simply omitting release-specific labels from its selector, rather than updating a service's selector to match the replication controller's selector fully. + A service can be made to span multiple deployments, such as is done across [rolling updates](/docs/tasks/run-application/rolling-update-replication-controller/), by simply omitting release-specific labels from its selector, rather than updating a service's selector to match the replication controller's selector fully. - To facilitate rolling updates, include version info in replication controller names, e.g. as a suffix to the name. It is useful to set a 'version' label as well. The rolling update creates a new controller as opposed to modifying the existing controller. So, there will be issues with - version-agnostic controller names. See the [documentation](/docs/user-guide/kubectl/kubectl_rolling-update/) on + version-agnostic controller names. See the [documentation](/docs/tasks/run-application/rolling-update-replication-controller/) on the rolling-update command for more detail. Note that the [Deployment](/docs/user-guide/deployments/) object obviates the need to manage replication @@ -89,7 +89,7 @@ This document is meant to highlight and consolidate in one place configuration b controller, or served traffic by a service, by removing the relevant selector labels. If you remove the labels of an existing pod, its controller will create a new pod to take its place. This is a useful way to debug a previously "live" pod in a quarantine environment. See the - [`kubectl label`](/docs/user-guide/kubectl/kubectl_label/) command. + [`kubectl label`](/docs/concepts/overview/working-with-objects/labels/) command. ## Container Images