diff options
| author | joe2far <joe2farrell@gmail.com> | 2016-07-13 15:06:24 +0100 |
|---|---|---|
| committer | joe2far <joe2farrell@gmail.com> | 2016-07-13 15:06:24 +0100 |
| commit | fa027eea67872811a0715c7c9c9db31b3b55ad62 (patch) | |
| tree | 7ae64c32aa10d9e74a27870f05eab9e960362fd8 /nodeaffinity.md | |
| parent | 9813b6e476becc5bebb82bfc5be4fbfa56b31cdd (diff) | |
Fixed several typos
Diffstat (limited to 'nodeaffinity.md')
| -rw-r--r-- | nodeaffinity.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/nodeaffinity.md b/nodeaffinity.md index 3c29d6fe..77bc6e91 100644 --- a/nodeaffinity.md +++ b/nodeaffinity.md @@ -62,7 +62,7 @@ scheduling requirements. rather than replacing `map[string]string`, due to backward compatibility requirements.) -The affiniy specifications described above allow a pod to request various +The affinity specifications described above allow a pod to request various properties that are inherent to nodes, for example "run this pod on a node with an Intel CPU" or, in a multi-zone cluster, "run this pod on a node in zone Z." ([This issue](https://github.com/kubernetes/kubernetes/issues/9044) describes |