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/tutorials/stateful-application/basic-stateful-set.md

@@ -22,7 +22,7 @@ Before you begin this tutorial, you should familiarize yourself with the
 following Kubernetes concepts.
 
 * [Pods](/docs/user-guide/pods/single-container/)
-* [Cluster DNS](/docs/admin/dns/)
+* [Cluster DNS](/docs/concepts/services-networking/dns-pod-service/)
 * [Headless Services](/docs/user-guide/services/#headless-services)
 * [PersistentVolumes](/docs/concepts/storage/volumes/)
 * [PersistentVolume Provisioning](http://releases.k8s.io/{{page.githubbranch}}/examples/persistent-volume-provisioning/)

docs/tutorials/stateful-application/run-replicated-stateful-application.md

@@ -28,11 +28,11 @@ on general patterns for running stateful applications in Kubernetes.
 * {% include task-tutorial-prereqs.md %}
 * {% include default-storage-class-prereqs.md %}
 * This tutorial assumes you are familiar with
-  [PersistentVolumes](/docs/user-guide/persistent-volumes/)
+  [PersistentVolumes](/docs/concepts/storage/persistent-volumes/)
   and [StatefulSets](/docs/concepts/abstractions/controllers/statefulsets/),
-  as well as other core concepts like [Pods](/docs/user-guide/pods/),
-  [Services](/docs/user-guide/services/), and
-  [ConfigMaps](/docs/user-guide/configmap/).
+  as well as other core concepts like [Pods](/docs/concepts/workloads/pods/pod/),
+  [Services](/docs/concepts/services-networking/service/), and
+  [ConfigMaps](/docs/tasks/configure-pod-container/configmap/).
 * Some familiarity with MySQL helps, but this tutorial aims to present
   general patterns that should be useful for other systems.
 

docs/tutorials/stateful-application/run-stateful-application.md

@@ -55,7 +55,7 @@ that points to the Compute Engine disk above:
 
 Notice that the `pdName: mysql-disk` line matches the name of the disk
 in the Compute Engine environment. See the
-[Persistent Volumes](/docs/user-guide/persistent-volumes/)
+[Persistent Volumes](/docs/concepts/storage/persistent-volumes/)
 for details on writing a PersistentVolume configuration file for other
 environments.
 
@@ -78,7 +78,7 @@ satisfied by any volume that meets the requirements, in this case, the
 volume created above.
 
 Note: The password is defined in the config yaml, and this is insecure. See
-[Kubernetes Secrets](/docs/user-guide/secrets/)
+[Kubernetes Secrets](/docs/concepts/configuration/secret/)
 for a secure solution.
 
 {% include code.html language="yaml" file="mysql-deployment.yaml" ghlink="/docs/tutorials/stateful-application/mysql-deployment.yaml" %}
@@ -180,7 +180,7 @@ specific to stateful apps:
 * Don't scale the app. This setup is for single-instance apps
   only. The underlying PersistentVolume can only be mounted to one
   Pod. For clustered stateful apps, see the
-  [StatefulSet documentation](/docs/user-guide/petset/).
+  [StatefulSet documentation](/docs/concepts/workloads/controllers/petset/).
 * Use `strategy:` `type: Recreate` in the Deployment configuration
   YAML file. This instructs Kubernetes to _not_ use rolling
   updates. Rolling updates will not work, as you cannot have more than
@@ -208,13 +208,13 @@ gcloud compute disks delete mysql-disk
 
 {% capture whatsnext %}
 
-* Learn more about [Deployment objects](/docs/user-guide/deployments/).
+* Learn more about [Deployment objects](/docs/concepts/workloads/controllers/deployment/).
 
 * Learn more about [Deploying applications](/docs/user-guide/deploying-applications/)
 
 * [kubectl run documentation](/docs/user-guide/kubectl/v1.6/#run)
 
-* [Volumes](/docs/concepts/storage/volumes/) and [Persistent Volumes](/docs/user-guide/persistent-volumes/)
+* [Volumes](/docs/concepts/storage/volumes/) and [Persistent Volumes](/docs/concepts/storage/persistent-volumes/)
 
 {% endcapture %}
 

docs/tutorials/stateful-application/zookeeper.md

@@ -23,11 +23,11 @@ Before starting this tutorial, you should be familiar with the following
 Kubernetes concepts.
 
 * [Pods](/docs/user-guide/pods/single-container/)
-* [Cluster DNS](/docs/admin/dns/)
+* [Cluster DNS](/docs/concepts/services-networking/dns-pod-service/)
 * [Headless Services](/docs/user-guide/services/#headless-services)
 * [PersistentVolumes](/docs/concepts/storage/volumes/)
 * [PersistentVolume Provisioning](http://releases.k8s.io/{{page.githubbranch}}/examples/persistent-volume-provisioning/)
-* [ConfigMaps](/docs/user-guide/configmap/)
+* [ConfigMaps](/docs/tasks/configure-pod-container/configmap/)
 * [StatefulSets](/docs/concepts/abstractions/controllers/statefulsets/)
 * [PodDisruptionBudgets](/docs/admin/disruptions/#specifying-a-poddisruptionbudget)
 * [PodAntiAffinity](/docs/user-guide/node-selection/#inter-pod-affinity-and-anti-affinity-beta-feature)
@@ -90,7 +90,7 @@ safely discarded.
 
 The manifest below contains a 
 [Headless Service](/docs/user-guide/services/#headless-services), 
-a [ConfigMap](/docs/user-guide/configmap/), 
+a [ConfigMap](/docs/tasks/configure-pod-container/configmap/), 
 a [PodDisruptionBudget](/docs/admin/disruptions/#specifying-a-poddisruptionbudget), 
 and a [StatefulSet](/docs/concepts/abstractions/controllers/statefulsets/). 
 
@@ -209,7 +209,7 @@ zk-1.zk-headless.default.svc.cluster.local
 zk-2.zk-headless.default.svc.cluster.local
 ```
 
-The A records in [Kubernetes DNS](/docs/admin/dns/) resolve the FQDNs to the Pods' IP addresses. 
+The A records in [Kubernetes DNS](/docs/concepts/services-networking/dns-pod-service/) resolve the FQDNs to the Pods' IP addresses. 
 If the Pods are rescheduled, the A records will be updated with the Pods' new IP 
 addresses, but the A record's names will not change.
 
@@ -726,7 +726,7 @@ container to rotate and ship your logs.
 The best practices with respect to allowing an application to run as a privileged 
 user inside of a container are a matter of debate. If your organization requires 
 that applications be run as a non-privileged user you can use a 
-[SecurityContext](/docs/user-guide/security-context/) to control the user that 
+[SecurityContext](/docs/concepts/policy/security-context/) to control the user that 
 the entry point runs as.
 
 The `zk` StatefulSet's Pod `template` contains a SecurityContext.