diff options
| author | Ed Costello <epc@epcostello.com> | 2015-10-29 14:36:29 -0400 |
|---|---|---|
| committer | Ed Costello <epc@epcostello.com> | 2015-12-22 09:30:48 -0500 |
| commit | f04f12d31546c069df69a9f706fef41542e51a6e (patch) | |
| tree | 5d16889d3a5351e2b3b429236722ee0b95a1a145 /daemon.md | |
| parent | 7bf6aa0fb999de2ed36df19227562a61251cd575 (diff) | |
Copy edits for typos
Diffstat (limited to 'daemon.md')
| -rw-r--r-- | daemon.md | 2 |
1 files changed, 1 insertions, 1 deletions
@@ -65,7 +65,7 @@ The DaemonSet supports standard API features: - Using the pod’s nodeSelector field, DaemonSets can be restricted to operate over nodes that have a certain label. For example, suppose that in a cluster some nodes are labeled ‘app=database’. You can use a DaemonSet to launch a datastore pod on exactly those nodes labeled ‘app=database’. - Using the pod's nodeName field, DaemonSets can be restricted to operate on a specified node. - The PodTemplateSpec used by the DaemonSet is the same as the PodTemplateSpec used by the Replication Controller. - - The initial implementation will not guarnatee that DaemonSet pods are created on nodes before other pods. + - The initial implementation will not guarantee that DaemonSet pods are created on nodes before other pods. - The initial implementation of DaemonSet does not guarantee that DaemonSet pods show up on nodes (for example because of resource limitations of the node), but makes a best effort to launch DaemonSet pods (like Replication Controllers do with pods). Subsequent revisions might ensure that DaemonSet pods show up on nodes, preempting other pods if necessary. - The DaemonSet controller adds an annotation "kubernetes.io/created-by: \<json API object reference\>" - YAML example: |