Update links to avoid redirects. (#5625)

2017-09-25 18:43:26 -07:00
parent f54f54ade6
commit 096fee2c39
15 changed files with 18 additions and 17 deletions
@@ -64,7 +64,7 @@ To access the deploy wizard from the Welcome page, click the respective button.

 The deploy wizard expects that you provide the following information:

- **App name** (mandatory): Name for your application. A [label](/docs/user-guide/labels/) with the name will be added to the Deployment and Service, if any, that will be deployed.
+- **App name** (mandatory): Name for your application. A [label](/docs/concepts/overview/working-with-objects/labels/) with the name will be added to the Deployment and Service, if any, that will be deployed.

  The application name must be unique within the selected Kubernetes [namespace](/docs/tasks/administer-cluster/namespaces/). It must start with a lowercase character, and end with a lowercase character or a number, and contain only lowercase letters, numbers and dashes (-). It is limited to 24 characters. Leading and trailing spaces are ignored.

@@ -84,7 +84,7 @@ If needed, you can expand the **Advanced options** section where you can specify

 - **Description**: The text you enter here will be added as an [annotation](/docs/concepts/overview/working-with-objects/annotations/) to the Deployment and displayed in the application's details.

- **Labels**: Default [labels](/docs/user-guide/labels/) to be used for your application are application name and version. You can specify additional labels to be applied to the Deployment, Service (if any), and Pods, such as release, environment, tier, partition, and release track.
+- **Labels**: Default [labels](/docs/concepts/overview/working-with-objects/labels/) to be used for your application are application name and version. You can specify additional labels to be applied to the Deployment, Service (if any), and Pods, such as release, environment, tier, partition, and release track.

  Example:

@@ -49,7 +49,7 @@ container, and if users use the [node
 allocatable](/docs/tasks/administer-cluster/reserve-compute-resources/#node-allocatable) feature, out of resource decisions
 are made local to the end user pod part of the cgroup hierarchy as well as the
 root node.  This
-[script](/docs/concepts/cluster-administration/out-of-resource/memory-available.sh)
+[script](/docs/tasks/administer-cluster/out-of-resource/memory-available.sh)
 reproduces the same set of steps that the `kubelet` performs to calculate
 `memory.available`. The `kubelet` excludes inactive_file (i.e. # of bytes of
 file-backed memory on inactive LRU list) from its calculation as it assumes that
@@ -75,7 +75,7 @@ a `disktype=ssd` label.

 {% capture whatsnext %}
 Learn more about
-[labels and selectors](/docs/user-guide/labels/).
+[labels and selectors](/docs/concepts/overview/working-with-objects/labels/).
 {% endcapture %}

 {% include templates/task.md %}
@@ -379,7 +379,7 @@ Learn about additional debugging tools, including:
 * [Logging](/docs/user-guide/logging/overview)
 * [Monitoring](/docs/user-guide/monitoring)
 * [Getting into containers via `exec`](/docs/user-guide/getting-into-containers)
-* [Connecting to containers via proxies](/docs/user-guide/connecting-to-applications-proxy)
+* [Connecting to containers via proxies](/docs/tasks/access-kubernetes-api/http-proxy-access-api/)
 * [Connecting to containers via port forwarding](/docs/user-guide/connecting-to-applications-port-forward)


@@ -109,7 +109,7 @@ Processing item cherry

 In the first example, each instance of the template had one parameter, and that parameter was also
 used as a label.  However label keys are limited in [what characters they can
-contain](/docs/user-guide/labels/#syntax-and-character-set).
+contain](/docs/concepts/overview/working-with-objects/labels/#syntax-and-character-set).

 This slightly more complex example uses the jinja2 template language to generate our objects.
 We will use a one-line python script to convert the template to a file.
@@ -159,7 +159,7 @@ causes:

 The rollout is stuck because new DaemonSet pods can't be scheduled on at least one
 node. This is possible when the node is 
-[running out of resources](/docs/concepts/cluster-administration/out-of-resource/).
+[running out of resources](/docs/tasks/administer-cluster/out-of-resource/).

 When this happens, find the nodes that don't have the DaemonSet pods scheduled on
 by comparing the output of `kubectl get nodes` and the output of: