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/tasks/debug-application-cluster/debug-init-containers.md

@@ -23,8 +23,8 @@ Init Containers.
 {% capture prerequisites %}
 
 * You should be familiar with the basics of
-  [Init Containers](/docs/user-guide/pods/init-container/).
-* You should have a [Pod](/docs/user-guide/pods/) you want to debug that uses
+  [Init Containers](/docs/concepts/abstractions/init-containers/).
+* You should have a [Pod](/docs/concepts/workloads/pods/pod/) you want to debug that uses
   Init Containers. The example command lines below refer to the Pod as
   `<pod-name>` and the Init Containers as `<init-container-1>` and
   `<init-container-2>`.

docs/tasks/debug-application-cluster/debug-pod-replication-controller.md

@@ -48,7 +48,7 @@ case you can try several things:
         kubectl get nodes -o yaml | grep '\sname\|cpu\|memory'
         kubectl get nodes -o json | jq '.items[] | {name: .metadata.name, cap: .status.capacity}'
 
-  The [resource quota](/docs/admin/resourcequota/)
+  The [resource quota](/docs/concepts/policy/resource-quotas/)
   feature can be configured to limit the total amount of
   resources that can be consumed. If used in conjunction with namespaces, it can
   prevent one team from hogging all the resources.

docs/tasks/debug-application-cluster/logging-elasticsearch-kibana.md

@@ -68,7 +68,7 @@ monitoring-influx-grafana-v1-o79xf             2/2       Running   0          2h
 
 The `fluentd-elasticsearch` pods gather logs from each node and send them to
 the `elasticsearch-logging` pods, which are part of a
-[service](/docs/user-guide/services/) named `elasticsearch-logging`. These
+[service](/docs/concepts/services-networking/service/) named `elasticsearch-logging`. These
 Elasticsearch pods store the logs and expose them via a REST API.
 The `kibana-logging` pod provides a web UI for reading the logs stored in
 Elasticsearch, and is part of a service named `kibana-logging`.

docs/tasks/debug-application-cluster/monitor-node-health.md

@@ -10,7 +10,7 @@ title: Monitoring Node Health
 
 ## Node Problem Detector
 
-*Node problem detector* is a [DaemonSet](/docs/admin/daemons/) monitoring the
+*Node problem detector* is a [DaemonSet](/docs/concepts/workloads/controllers/daemonset/) monitoring the
 node health. It collects node problems from various daemons and reports them
 to the apiserver as [NodeCondition](/docs/admin/node/#node-condition) and
 [Event](/docs/api-reference/v1.6/#event-v1-core).
@@ -120,7 +120,7 @@ Just create `node-problem-detector.yaml`, and put it under the addon pods direct
 The [default configuration](https://github.com/kubernetes/node-problem-detector/tree/v0.1/config)
 is embedded when building the docker image of node problem detector.
 
-However, you can use [ConfigMap](/docs/user-guide/configmap/) to overwrite it
+However, you can use [ConfigMap](/docs/tasks/configure-pod-container/configmap/) to overwrite it
 following the steps:
 
 * **Step 1:** Change the config files in `config/`.