Update links to avoid redirect.s (#5829)

docs/concepts/cluster-administration/cluster-administration-overview.md

@@ -34,7 +34,7 @@ If you are using a guide involving Salt, see [Configuring Kubernetes with Salt](
 
 ## Managing a cluster
 
-* [Managing a cluster](/docs/concepts/cluster-administration/cluster-management/) describes several topics related to the lifecycle of a cluster: creating a new cluster, upgrading your cluster’s master and worker nodes, performing node maintenance (e.g. kernel upgrades), and upgrading the Kubernetes API version of a running cluster.
+* [Managing a cluster](/docs/tasks/administer-cluster/cluster-management/) describes several topics related to the lifecycle of a cluster: creating a new cluster, upgrading your cluster’s master and worker nodes, performing node maintenance (e.g. kernel upgrades), and upgrading the Kubernetes API version of a running cluster.
 
 * Learn how to [manage nodes](/docs/concepts/nodes/node/).
 

docs/concepts/overview/kubernetes-api.md

@@ -10,7 +10,7 @@ API endpoints, resource types and samples are described in [API Reference](/docs
 
 Remote access to the API is discussed in the [access doc](/docs/admin/accessing-the-api).
 
-The Kubernetes API also serves as the foundation for the declarative configuration schema for the system. The [Kubectl](/docs/user-guide/kubectl) command-line tool can be used to create, update, delete, and get API objects.
+The Kubernetes API also serves as the foundation for the declarative configuration schema for the system. The [Kubectl](/docs/user-guide/kubectl/) command-line tool can be used to create, update, delete, and get API objects.
 
 Kubernetes also stores its serialized state (currently in [etcd](https://coreos.com/docs/distributed-configuration/getting-started-with-etcd/)) in terms of the API resources.
 

docs/concepts/overview/working-with-objects/kubernetes-objects.md

@@ -61,7 +61,7 @@ You'll also need to provide the object `spec` field. The precise format of the o
 {% endcapture %}
 
 {% capture whatsnext %}
-* Learn about the most important basic Kubernetes objects, such as [Pod](/docs/concepts/abstractions/pod/).
+* Learn about the most important basic Kubernetes objects, such as [Pod](/docs/concepts/workloads/pods/pod-overview/).
 {% endcapture %}
 
 {% include templates/concept.md %}

docs/concepts/overview/working-with-objects/namespaces.md

@@ -72,7 +72,7 @@ $ kubectl config view | grep namespace:
 
 ## Namespaces and DNS
 
-When you create a [Service](/docs/user-guide/services), it creates a corresponding [DNS entry](/docs/admin/dns).
+When you create a [Service](/docs/user-guide/services), it creates a corresponding [DNS entry](/docs/concepts/services-networking/dns-pod-service/).
 This entry is of the form `<service-name>.<namespace-name>.svc.cluster.local`, which means
 that if a container just uses `<service-name>`, it will resolve to the service which
 is local to a namespace.  This is useful for using the same configuration across

docs/concepts/workloads/pods/init-containers.md

@@ -20,7 +20,7 @@ In 1.8, the annotations are no longer supported and must be converted to the Pod
 {% capture body %}
 ## Understanding Init Containers
 
-A [Pod](/docs/concepts/abstractions/pod/) can have multiple Containers running
+A [Pod](/docs/concepts/workloads/pods/pod-overview/) can have multiple Containers running
 apps within it, but it can also have one or more Init Containers, which are run
 before the app Containers are started.
 

docs/getting-started-guides/aws.md

@@ -38,7 +38,7 @@ export PATH=<path/to/kubernetes-directory>/platforms/darwin/amd64:$PATH
 export PATH=<path/to/kubernetes-directory>/platforms/linux/amd64:$PATH
 ```
 
-An up-to-date documentation page for this tool is available here: [kubectl manual](/docs/user-guide/kubectl)
+An up-to-date documentation page for this tool is available here: [kubectl manual](/docs/user-guide/kubectl/)
 
 By default, `kubectl` will use the `kubeconfig` file generated during the cluster startup for authenticating against the API.
 For more information, please read [kubeconfig files](/docs/tasks/access-application-cluster/configure-access-multiple-clusters/)

docs/tasks/administer-cluster/namespaces.md

@@ -334,7 +334,7 @@ Use cases include:
 
 ## Understanding namespaces and DNS
 
-When you create a [Service](/docs/concepts/services-networking/service/), it creates a corresponding [DNS entry](/docs/admin/dns).
+When you create a [Service](/docs/concepts/services-networking/service/), it creates a corresponding [DNS entry](/docs/concepts/services-networking/dns-pod-service/).
 This entry is of the form `<service-name>.<namespace-name>.svc.cluster.local`, which means
 that if a container just uses `<service-name>` it will resolve to the service which
 is local to a namespace.  This is useful for using the same configuration across

docs/tasks/extend-kubectl/kubectl-plugins.md

@@ -9,7 +9,7 @@ description: With kubectl plugins, you can extend the functionality of the kubec
 
 {% include feature-state-alpha.md %}
 
-This guide shows you how to install and write extensions for [kubectl](/docs/user-guide/kubectl). Usually called *plugins* or *binary extensions*, this feature allows you to extend the default set of commands available in `kubectl` by adding new subcommands to perform new tasks and extend the set of features available in the main distribution of `kubectl`.
+This guide shows you how to install and write extensions for [kubectl](/docs/user-guide/kubectl/). Usually called *plugins* or *binary extensions*, this feature allows you to extend the default set of commands available in `kubectl` by adding new subcommands to perform new tasks and extend the set of features available in the main distribution of `kubectl`.
 
 {% endcapture %}
 

docs/tasks/tools/install-kubectl.md

@@ -6,7 +6,7 @@ title: Install and Set Up kubectl
 ---
 
 {% capture overview %}
-Use the Kubernetes command-line tool, [kubectl](/docs/user-guide/kubectl), to deploy and manage applications on Kubernetes. Using kubectl, you can inspect cluster resources; create, delete, and update components; and look at your new cluster and bring up example apps.
+Use the Kubernetes command-line tool, [kubectl](/docs/user-guide/kubectl/), to deploy and manage applications on Kubernetes. Using kubectl, you can inspect cluster resources; create, delete, and update components; and look at your new cluster and bring up example apps.
 {% endcapture %}
 
 {% capture prerequisites %}

docs/tutorials/stateful-application/basic-stateful-set.md

@@ -25,7 +25,7 @@ following Kubernetes concepts.
 * [PersistentVolumes](/docs/concepts/storage/persistent-volumes/)
 * [PersistentVolume Provisioning](https://github.com/kubernetes/examples/tree/{{page.githubbranch}}/staging/persistent-volume-provisioning/)
 * [StatefulSets](/docs/concepts/workloads/controllers/statefulset/)
-* [kubectl CLI](/docs/user-guide/kubectl)
+* [kubectl CLI](/docs/user-guide/kubectl/)
 
 This tutorial assumes that your cluster is configured to dynamically provision 
 PersistentVolumes. If your cluster is not configured to do so, you

docs/tutorials/stateful-application/zookeeper.md

@@ -30,7 +30,7 @@ Kubernetes concepts.
 * [StatefulSets](/docs/concepts/workloads/controllers/statefulset/)
 * [PodDisruptionBudgets](/docs/concepts/workloads/pods/disruptions/#specifying-a-poddisruptionbudget)
 * [PodAntiAffinity](/docs/user-guide/node-selection/#inter-pod-affinity-and-anti-affinity-beta-feature)
-* [kubectl CLI](/docs/user-guide/kubectl)
+* [kubectl CLI](/docs/user-guide/kubectl/)
 
 You will require a cluster with at least four nodes, and each node will require
 at least 2 CPUs and 4 GiB of memory. In this tutorial you will cordon and 

docs/user-guide/kubectl-overview.md

@@ -5,7 +5,7 @@ approvers:
 title: Overview of kubectl
 ---
 
-`kubectl` is a command line interface for running commands against Kubernetes clusters. This overview covers `kubectl` syntax, describes the command operations, and provides common examples. For details about each command, including all the supported flags and subcommands, see the [kubectl](/docs/user-guide/kubectl) reference documentation. For installation instructions see [installing kubectl](/docs/tasks/kubectl/install/).
+`kubectl` is a command line interface for running commands against Kubernetes clusters. This overview covers `kubectl` syntax, describes the command operations, and provides common examples. For details about each command, including all the supported flags and subcommands, see the [kubectl](/docs/user-guide/kubectl/) reference documentation. For installation instructions see [installing kubectl](/docs/tasks/kubectl/install/).
 
 ## Syntax
 
@@ -78,7 +78,7 @@ Operation       | Syntax    |       Description
 `stop`        | `kubectl stop` | Deprecated: Instead, see `kubectl delete`.
 `version`        | `kubectl version [--client] [flags]` | Display the Kubernetes version running on the client and server.
 
-Remember: For more about command operations, see the [kubectl](/docs/user-guide/kubectl) reference documentation.
+Remember: For more about command operations, see the [kubectl](/docs/user-guide/kubectl/) reference documentation.
 
 ## Resource types
 
@@ -127,7 +127,7 @@ Resource type    | Abbreviated alias
 
 ## Output options
 
-Use the following sections for information about how you can format or sort the output of certain commands. For details about which commands support the various output options, see the [kubectl](/docs/user-guide/kubectl) reference documentation.
+Use the following sections for information about how you can format or sort the output of certain commands. For details about which commands support the various output options, see the [kubectl](/docs/user-guide/kubectl/) reference documentation.
 
 ### Formatting output
 
@@ -158,7 +158,7 @@ In this example, the following command outputs the details for a single pod as a
 
 `$ kubectl get pod web-pod-13je7 -o=yaml`
 
-Remember: See the [kubectl](/docs/user-guide/kubectl) reference documentation for details about which output format is supported by each command.
+Remember: See the [kubectl](/docs/user-guide/kubectl/) reference documentation for details about which output format is supported by each command.
 
 #### Custom columns
 
@@ -302,4 +302,4 @@ $ kubectl logs -f <pod-name>
 
 ## Next steps
 
-Start using the [kubectl](/docs/user-guide/kubectl) commands.
+Start using the [kubectl](/docs/user-guide/kubectl/) commands.

docs/user-guide/walkthrough/index.md

@@ -161,5 +161,5 @@ Finally, we have also introduced an environment variable to the `git-monitor` co
 
 ## What's Next?
 
-Continue on to [Kubernetes 201](/docs/user-guide/walkthrough/k8s201) or
+Continue on to [Kubernetes 201](/docs/user-guide/walkthrough/k8s201/) or
 for a complete application see the [guestbook example](https://github.com/kubernetes/examples/tree/{{page.githubbranch}}/guestbook/)