diff options
| author | Denis Andrejew <da.colonel@gmail.com> | 2016-10-07 12:48:02 +0200 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2016-10-07 12:48:02 +0200 |
| commit | e66185b8628300bedfd68f7b886343a027acb44d (patch) | |
| tree | 30816ae76a63bfc84e382c9a5ec0da707f6275d5 | |
| parent | bf5cb84fa95379462fb0934686e415d0a61745f2 (diff) | |
fix typo in podaffinity.md
| -rw-r--r-- | podaffinity.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/podaffinity.md b/podaffinity.md index 33eaf60d..d9796cd9 100644 --- a/podaffinity.md +++ b/podaffinity.md @@ -213,7 +213,7 @@ are satisfied for each node, and the node(s) with the highest weight(s) are the most preferred. In reality there are two variants of `RequiredDuringScheduling`: one suffixed -with `RequiredDuringEecution` and one suffixed with `IgnoredDuringExecution`. +with `RequiredDuringExecution` and one suffixed with `IgnoredDuringExecution`. For the first variant, if the affinity/anti-affinity ceases to be met at some point during pod execution (e.g. due to a pod label update), the system will try to eventually evict the pod from its node. In the second variant, the system may |