diff options
| author | Klaus Ma <k82cn@icloud.com> | 2017-02-07 07:54:50 +0800 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2017-02-07 07:54:50 +0800 |
| commit | 4d95b6c0c4aee0626bc134f78385cc6faa40ea00 (patch) | |
| tree | fdf81dba875214df66df3cd20b8298785daf9fc6 | |
| parent | a7a93b05e8d0f1be65e8a5cc21ae15e9cc1deab7 (diff) | |
| parent | 135a1fdde3ac39489a070a70c4b940ceb59f92ba (diff) | |
Merge pull request #334 from gyliu513/rescheduling
Fixed typo in rescheduling.md.
| -rw-r--r-- | contributors/design-proposals/rescheduling.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/contributors/design-proposals/rescheduling.md b/contributors/design-proposals/rescheduling.md index b1bdb937..1966de79 100644 --- a/contributors/design-proposals/rescheduling.md +++ b/contributors/design-proposals/rescheduling.md @@ -52,7 +52,7 @@ Example use cases for rescheduling are * (note that these last two cases are the only use cases where the first-order intent is to move a pod specifically for the benefit of another pod) * moving a running pod off of a node from which it is receiving poor service - * anomalous crashlooping or other mysterious incompatiblity between the pod and the node + * anomalous crashlooping or other mysterious incompatibility between the pod and the node * repeated out-of-resource killing (see #18724) * repeated attempts by the scheduler to schedule the pod onto some node, but it is rejected by Kubelet admission control due to incomplete scheduler knowledge |