Update User Guide and Admin links to point to new resources. (#3438)

* Update links to outdated user-guide and admin docs

* Add script for updating outdated links.

* Update regex to include init-containers file.

* Pull upstream, rewrite links in and to namespaces walkthrough.

docs/getting-started-guides/clc.md

@@ -269,7 +269,7 @@ distributed with OSX.
 ### Accessing the cluster with a browser
 
 We install two UIs on Kubernetes. The original KubeUI and [the newer kube
-dashboard](/docs/user-guide/ui/). When you create a cluster, the script should output URLs for these
+dashboard](/docs/tasks/web-ui-dashboard/). When you create a cluster, the script should output URLs for these
 interfaces like this:
 
 KubeUI is running at ```https://${MASTER_IP}:6443/api/v1/namespaces/kube-system/services/kube-ui/proxy```
@@ -323,7 +323,7 @@ Then, you can access urls like ```http://127.0.0.1:8001/api/v1/namespaces/kube-s
 
 These are the known items that don't work on CenturyLink cloud but do work on other cloud providers:
 
-- At this time, there is no support services of the type [LoadBalancer](/docs/user-guide/load-balancer/). We are actively working on this and hope to publish the changes sometime around April 2016.
+- At this time, there is no support services of the type [LoadBalancer](/docs/tasks/access-application-cluster/create-external-load-balancer/). We are actively working on this and hope to publish the changes sometime around April 2016.
 
 - At this time, there is no support for persistent storage volumes provided by
   CenturyLink Cloud. However, customers can bring their own persistent storage

docs/getting-started-guides/fedora/fedora_manual_config.md

@@ -17,7 +17,7 @@ title: Fedora (Single Node)
 
 This is a getting started guide for Fedora.  It is a manual configuration so you understand all the underlying packages / services / ports, etc...
 
-This guide will only get ONE node (previously minion) working.  Multiple nodes require a functional [networking configuration](/docs/admin/networking/) done outside of Kubernetes.  Although the additional Kubernetes configuration requirements should be obvious.
+This guide will only get ONE node (previously minion) working.  Multiple nodes require a functional [networking configuration](/docs/concepts/cluster-administration/networking/) done outside of Kubernetes.  Although the additional Kubernetes configuration requirements should be obvious.
 
 The Kubernetes package provides a few services: kube-apiserver, kube-scheduler, kube-controller-manager, kubelet, kube-proxy.  These services are managed by systemd and the configuration resides in a central location: /etc/kubernetes.  We will break the services up between the hosts.  The first host, fed-master, will be the Kubernetes master.  This host will run the kube-apiserver, kube-controller-manager, and kube-scheduler.  In addition, the master will also run _etcd_ (not needed if _etcd_ runs on a different host but this guide assumes that _etcd_ and Kubernetes master run on the same host).  The remaining host, fed-node will be the node and run kubelet, proxy and docker.
 

docs/getting-started-guides/kops.md

@@ -145,7 +145,7 @@ for production clusters!
 
 ### Explore other add-ons
 
-See the [list of add-ons](/docs/admin/addons/) to explore other add-ons, including tools for logging, monitoring, network policy, visualization & control of your Kubernetes cluster.
+See the [list of add-ons](/docs/concepts/cluster-administration/addons/) to explore other add-ons, including tools for logging, monitoring, network policy, visualization & control of your Kubernetes cluster.
 
 ## What's next
 

docs/getting-started-guides/rkt/index.md

@@ -21,7 +21,7 @@ This document describes how to run Kubernetes using [rkt](https://github.com/cor
 
 ### Kubernetes CNI networking
 
-You can configure Kubernetes pod networking with the usual Container Network Interface (CNI) [network plugins](/docs/admin/network-plugins/) by setting the kubelet's `--network-plugin` and `--network-plugin-dir` options appropriately. Configured in this fashion, the rkt container engine will be unaware of network details, and expects to connect pods to the provided subnet.
+You can configure Kubernetes pod networking with the usual Container Network Interface (CNI) [network plugins](/docs/concepts/cluster-administration/network-plugins/) by setting the kubelet's `--network-plugin` and `--network-plugin-dir` options appropriately. Configured in this fashion, the rkt container engine will be unaware of network details, and expects to connect pods to the provided subnet.
 
 #### kubenet: Google Compute Engine (GCE) network
 

docs/getting-started-guides/scratch.md

@@ -132,7 +132,7 @@ Also, you need to pick a static IP for master node.
 
 Kubernetes enables the definition of fine-grained network policy between Pods using the [NetworkPolicy](/docs/concepts/services-networking/networkpolicies/) resource.
 
-Not all networking providers support the Kubernetes NetworkPolicy API, see [Using Network Policy](/docs/getting-started-guides/network-policy/walkthrough/) for more information.
+Not all networking providers support the Kubernetes NetworkPolicy API, see [Using Network Policy](/docs/tasks/configure-pod-container/declare-network-policy/) for more information.
 
 ### Cluster Naming
 
@@ -822,7 +822,7 @@ Notes for setting up each cluster service are given below:
 * Cluster DNS:
   * required for many Kubernetes examples
   * [Setup instructions](http://releases.k8s.io/{{page.githubbranch}}/cluster/addons/dns/)
-  * [Admin Guide](/docs/admin/dns/)
+  * [Admin Guide](/docs/concepts/services-networking/dns-pod-service/)
 * Cluster-level Logging
   * [Cluster-level Logging Overview](/docs/user-guide/logging/overview)
   * [Cluster-level Logging with Elasticsearch](/docs/user-guide/logging/elasticsearch)