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/administer-federation/configmap.md

@@ -20,12 +20,12 @@ might also help you create a Federated Kubernetes cluster.
 
 You should also have a basic
 [working knowledge of Kubernetes](/docs/getting-started-guides/) in
-general and [ConfigMaps](/docs/user-guide/configmap/) in particular.
+general and [ConfigMaps](/docs/tasks/configure-pod-container/configmap/) in particular.
 
 ## Overview
 
 Federated ConfigMaps are very similar to the traditional [Kubernetes
-ConfigMaps](/docs/user-guide/configmap/) and provide the same functionality.
+ConfigMaps](/docs/tasks/configure-pod-container/configmap/) and provide the same functionality.
 Creating them in the federation control plane ensures that they are synchronized
 across all the clusters in federation.
 

docs/tasks/administer-federation/ingress.md

@@ -40,12 +40,12 @@ by Kelsey Hightower, are also available to help you.
 
 You are also expected to have a basic
 [working knowledge of Kubernetes](/docs/getting-started-guides/) in
-general, and [Ingress](/docs/user-guide/ingress/) in particular.
+general, and [Ingress](/docs/concepts/services-networking/ingress/) in particular.
 
 ## Overview
 
 Federated Ingresses are created in much that same way as traditional
-[Kubernetes Ingresses](/docs/user-guide/ingress/): by making an API
+[Kubernetes Ingresses](/docs/concepts/services-networking/ingress/): by making an API
 call which specifies the desired properties of your logical ingress point. In the
 case of Federated Ingress, this API call is directed to the
 Federation API endpoint, rather than a Kubernetes cluster API
@@ -87,7 +87,7 @@ You can create a federated ingress in any of the usual ways, for example using k
 ``` shell
 kubectl --context=federation-cluster create -f myingress.yaml
 ```
-For example ingress YAML configurations, see the [Ingress User Guide](/docs/user-guide/ingress/)
+For example ingress YAML configurations, see the [Ingress User Guide](/docs/concepts/services-networking/ingress/)
 The '--context=federation-cluster' flag tells kubectl to submit the
 request to the Federation API endpoint, with the appropriate
 credentials. If you have not yet configured such a context, visit the

docs/tasks/administer-federation/namespaces.md

@@ -19,13 +19,13 @@ by Kelsey Hightower, are also available to help you.
 
 You are also expected to have a basic
 [working knowledge of Kubernetes](/docs/getting-started-guides/) in
-general and [Namespaces](/docs/user-guide/namespaces/) in particular.
+general and [Namespaces](/docs/concepts/overview/working-with-objects/namespaces/) in particular.
 
 ## Overview
 
 Namespaces in federation control plane (referred to as "federated namespaces" in
 this guide) are very similar to the traditional [Kubernetes
-Namespaces](/docs/user-guide/namespaces/) providing the same functionality.
+Namespaces](/docs/concepts/overview/working-with-objects/namespaces/) providing the same functionality.
 Creating them in the federation control plane ensures that they are synchronized
 across all the clusters in federation.
 

docs/tasks/administer-federation/replicaset.md

@@ -19,13 +19,13 @@ by Kelsey Hightower, are also available to help you.
 
 You are also expected to have a basic
 [working knowledge of Kubernetes](/docs/getting-started-guides/) in
-general and [ReplicaSets](/docs/user-guide/replicasets/) in particular.
+general and [ReplicaSets](/docs/concepts/workloads/controllers/replicaset/) in particular.
 
 ## Overview
 
 Replica Sets in federation control plane (referred to as "federated replica sets" in
 this guide) are very similar to the traditional [Kubernetes
-ReplicaSets](/docs/user-guide/replicasets/), and provide the same functionality.
+ReplicaSets](/docs/concepts/workloads/controllers/replicaset/), and provide the same functionality.
 Creating them in the federation control plane ensures that the desired number of
 replicas exist across the registered clusters.
 

docs/tasks/administer-federation/secret.md

@@ -19,13 +19,13 @@ by Kelsey Hightower, are also available to help you.
 
 You are also expected to have a basic
 [working knowledge of Kubernetes](/docs/getting-started-guides/) in
-general and [Secrets](/docs/user-guide/secrets/) in particular.
+general and [Secrets](/docs/concepts/configuration/secret/) in particular.
 
 ## Overview
 
 Secrets in federation control plane (referred to as "federated secrets" in
 this guide) are very similar to the traditional [Kubernetes
-Secrets](/docs/user-guide/secrets/) providing the same functionality.
+Secrets](/docs/concepts/configuration/secret/) providing the same functionality.
 Creating them in the federation control plane ensures that they are synchronized
 across all the clusters in federation.