From 9e94cd5530b573792e0df93ba23007542c613977 Mon Sep 17 00:00:00 2001 From: Steve Perry Date: Wed, 4 Oct 2017 17:50:18 -0700 Subject: [PATCH] Fix broken links. (#5770) --- docs/concepts/overview/working-with-objects/labels.md | 2 +- docs/concepts/workloads/controllers/replicaset.md | 2 +- docs/tasks/federation/set-up-cluster-federation-kubefed.md | 4 ++-- 3 files changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/concepts/overview/working-with-objects/labels.md b/docs/concepts/overview/working-with-objects/labels.md index b66085fca7..8e577c87e4 100644 --- a/docs/concepts/overview/working-with-objects/labels.md +++ b/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/concepts/configuration/assign-pods-nodes/) for more information. +See the documentation on [node selection](/docs/concepts/configuration/assign-pod-node/) for more information. diff --git a/docs/concepts/workloads/controllers/replicaset.md b/docs/concepts/workloads/controllers/replicaset.md index 3a76afd128..acdfea5ac5 100644 --- a/docs/concepts/workloads/controllers/replicaset.md +++ b/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/concepts/overview/working-with-objects/#label-selectors). A ReplicaSet +The `.spec.selector` field is a [label selector](/docs/concepts/overview/working-with-objects/labels/). 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. diff --git a/docs/tasks/federation/set-up-cluster-federation-kubefed.md b/docs/tasks/federation/set-up-cluster-federation-kubefed.md index 1874f61235..fb23af29a6 100644 --- a/docs/tasks/federation/set-up-cluster-federation-kubefed.md +++ b/docs/tasks/federation/set-up-cluster-federation-kubefed.md @@ -383,7 +383,7 @@ for the federation control plane's host cluster. > Note: The name that you provide to the `join` command is used as the joining cluster's identity in federation. This name should adhere to the rules described in the -[identifiers doc](docs/concepts/overview/working-with-objects/names/). If the context +[identifiers doc](/docs/concepts/overview/working-with-objects/names/). If the context corresponding to your joining cluster conforms to these rules then you can use the same name in the join command. Otherwise, you will have to choose a different name for your cluster's identity. For more @@ -408,7 +408,7 @@ cluster. The cluster name you supply to `kubefed join` must be a valid [RFC 1035](https://www.ietf.org/rfc/rfc1035.txt) label and are -enumerated in the [Identifiers doc](docs/concepts/overview/working-with-objects/names/). +enumerated in the [Identifiers doc](/docs/concepts/overview/working-with-objects/names/). Furthermore, federation control plane requires credentials of the joined clusters to operate on them. These credentials are obtained