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/reference/deprecation-policy.md

@@ -19,7 +19,7 @@ This document details the deprecation policy for various facets of the system.
 Since Kubernetes is an API-driven system, the API has evolved over time to
 reflect the evolving understanding of the problem space. The Kubernetes API is
 actually a set of APIs, called "API groups", and each API group is
-independently versioned.  [API versions](http://kubernetes.io/docs/api/) fall
+independently versioned.  [API versions](/docs/reference/api-overview/#api-versioning) fall
 into 3 main tracks, each of which has different policies for deprecation:
 
 | Example  | Track                            |
@@ -175,7 +175,7 @@ versions are supported in a series of subsequent releases.
 
 Consider a hypothetical REST resource named Widget, which was present in API v1
 in the above timeline, and which needs to be deprecated.  We
-[document](http://kubernetes.io/docs/deprecated/) and
+[document](/docs/reference/deprecation-policy/) and
 [announce](https://groups.google.com/forum/#!forum/kubernetes-announce) the
 deprecation in sync with release X+1.  The Widget resource still exists in API
 version v1 (deprecated) but not in v2alpha1.  The Widget resource continues to