Update links to avoid redirects. (#5763)

docs/concepts/cluster-administration/federation.md

@@ -34,7 +34,7 @@ why you might want multiple clusters are:
 * Fault isolation: It might be better to have multiple small clusters rather
   than a single large  cluster for fault isolation (for example: multiple
   clusters in different availability zones of a cloud provider).
-  See [Multi cluster guide](/docs/admin/multi-cluster) for details.
+  See [Multi cluster guide](/docs/concepts/cluster-administration/federation/) for details.
 * Scalability: There are scalability limits to a single kubernetes cluster (this
   should not be the case for most users. For more details:
   [Kubernetes Scaling and Performance Goals](https://git.k8s.io/community/sig-scalability/goals.md)).

docs/concepts/overview/working-with-objects/labels.md

@@ -170,4 +170,4 @@ selector:
 #### Selecting sets of nodes
 
 One use case for selecting over labels is to constrain the set of nodes onto which a pod can schedule.
-See the documentation on [node selection](/docs/user-guide/node-selection) for more information.
+See the documentation on [node selection](/docs/concepts/configuration/assign-pods-nodes/) for more information.

docs/concepts/workloads/controllers/replicaset.md

@@ -119,7 +119,7 @@ for example the [Kubelet](/docs/admin/kubelet/) or Docker.
 
 ### Pod Selector
 
-The `.spec.selector` field is a [label selector](/docs/user-guide/labels/#label-selectors). A ReplicaSet
+The `.spec.selector` field is a [label selector](/docs/concepts/overview/working-with-objects/#label-selectors). A ReplicaSet
 manages all the pods with labels that match the selector. It does not distinguish
 between pods that it created or deleted and pods that another person or process created or
 deleted. This allows the ReplicaSet to be replaced without affecting the running pods.