whentimeslows/website
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Fix broken links. (#5770)

Browse Source
This commit is contained in:
Steve Perry
2017-10-04 17:50:18 -07:00
committed by GitHub
parent 95d3e80540
commit 9e94cd5530
3 changed files with 4 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/concepts/overview/working-with-objects/labels.md
+1 -1
View File
@@ -170,4 +170,4 @@ selector:
#### Selecting sets of nodes #### Selecting sets of nodes
One use case for selecting over labels is to constrain the set of nodes onto which a pod can schedule. 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.
docs/concepts/workloads/controllers/replicaset.md
+1 -1
View File
@@ -119,7 +119,7 @@ for example the [Kubelet](/docs/admin/kubelet/) or Docker.
### Pod Selector ### 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 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 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. deleted. This allows the ReplicaSet to be replaced without affecting the running pods.
docs/tasks/federation/set-up-cluster-federation-kubefed.md
+2 -2
View File
@@ -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 > 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 joining cluster's identity in federation. This name should adhere to
the rules described in the 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 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 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 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 The cluster name you supply to `kubefed join` must be a valid
[RFC 1035](https://www.ietf.org/rfc/rfc1035.txt) label and are [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 Furthermore, federation control plane requires credentials of the
joined clusters to operate on them. These credentials are obtained joined clusters to operate on them. These credentials are obtained