Remove self-links with domain names in docs (#4299)

* Remove self-links with domain names in docs

Fixes #4191. Skipping the tutorials we import from kubernetes/examples.

Signed-off-by: Ahmet Alp Balkan <ahmetb@google.com>

* update federation/index.md user-guide links

* update assign-pod-node.md links

* update dns-pod-service.md link

* update link in jobs-run-to-completion.md

* update link in minikube.md

* update PS link in minikube.md

* update links in stackpoint.md

* update links in storage.md

* fix link in vsphere.md

* fix links in deprecation-policy.md

* Update pick-right-solution.md

* Update web-ui-dashboard.md

* Update ingress.md

* Update federation-service-discovery.md

* Update user-guide.md

* Update expose-external-ip-address.md

* Update README.md

* Update README.md

docs/getting-started-guides/ubuntu/local.md

@@ -6,7 +6,7 @@ title: Local Kubernetes development with LXD
 Running Kubernetes locally has obvious development advantages, such as lower cost and faster iteration than constantly deploying and tearing down clusters on a public cloud. Ideally, a Kubernetes developer can spawn all necessary nodes inside local containers and test new configurations as they are committed. This page will show you how to deploy a cluster to LXD containers on a local machine.
 {% endcapture %}
 
-The purpose of using [LXD](https://linuxcontainers.org/lxd/) on a local machine is to emulate the same deployment that a user would use in a cloud or bare metal. Each node is treated as a machine, with the same characteristics as production. Each node is a separate container, which runs Docker containers and `kubectl` inside (see [Cluster Intro](https://kubernetes.io/docs/tutorials/kubernetes-basics/cluster-intro/) for more info).
+The purpose of using [LXD](https://linuxcontainers.org/lxd/) on a local machine is to emulate the same deployment that a user would use in a cloud or bare metal. Each node is treated as a machine, with the same characteristics as production. Each node is a separate container, which runs Docker containers and `kubectl` inside (see [Cluster Intro](/docs/tutorials/kubernetes-basics/cluster-intro/) for more info).
 
 {% capture prerequisites %}
 Install [conjure-up](http://conjure-up.io/), a tool for deploying big software.

docs/getting-started-guides/ubuntu/manual.md

@@ -123,7 +123,7 @@ through `FLANNEL_BACKEND` and `FLANNEL_OTHER_NET_CONFIG`, as explained in `clust
 The default setting for `ADMISSION_CONTROL` is right for the latest
 release of Kubernetes, but if you choose an earlier release then you
 might want a different setting.  See
-[the admission control doc](http://kubernetes.io/docs/admin/admission-controllers/#is-there-a-recommended-set-of-plug-ins-to-use)
+[the admission control doc](/docs/admin/admission-controllers/#is-there-a-recommended-set-of-plug-ins-to-use)
 for the recommended settings for various releases.
 
 **Note:** When deploying, master needs to be connected to the Internet to download the necessary files.

docs/getting-started-guides/ubuntu/scaling.md

@@ -22,7 +22,7 @@ The provided Kubernetes master nodes act as a control plane for the cluster. The
 
     juju add-unit kubernetes-master
 
-This will add another master node to the control plane. See the [building high-availability clusters](http://kubernetes.io/docs/admin/high-availability) section of the documentation for more information. 
+This will add another master node to the control plane. See the [building high-availability clusters](/docs/admin/high-availability) section of the documentation for more information. 
 
 ## Kubernetes workers
 

docs/getting-started-guides/ubuntu/storage.md

@@ -60,7 +60,7 @@ juju add-relation kubernetes-master ceph-mon
 ```
 
 We are now ready to enlist 
-[Persistent Volumes](http://kubernetes.io/docs/user-guide/persistent-volumes/)
+[Persistent Volumes](/docs/concepts/storage/persistent-volumes/)
 in Kubernetes which our workloads can consume via Persistent Volume (PV) claims.
 
 ```
@@ -84,8 +84,8 @@ test   50M          RWO       Available                              10s
 
 To consume these Persistent Volumes, your pods will need an associated
 Persistent Volume Claim with them, and is outside the scope of this README. See the
-[Persistent Volumes](http://kubernetes.io/docs/user-guide/persistent-volumes/)
+[Persistent Volumes](/docs/concepts/storage/persistent-volumes/)
 documentation for more information.
 {% endcapture %}
 
-{% include templates/task.md %}
+{% include templates/task.md %}