diff options
| author | Kubernetes Submit Queue <k8s-merge-robot@users.noreply.github.com> | 2017-10-06 10:30:33 -0700 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2017-10-06 10:30:33 -0700 |
| commit | aab1ceb21501beef8b692ac265dfc65e8150e354 (patch) | |
| tree | cdbcb41b8b0be5a97b20f96abf311a5f3eb4985c | |
| parent | ad4e73adaa56fb86e6973097c625ec4175efc933 (diff) | |
| parent | 43d291131bc9bd0f05761a5a65c3e790e9a39b7e (diff) | |
Merge pull request #1158 from huzhengchuan/patch-1
Automatic merge from submit-queue.
Fix typos
| -rw-r--r-- | contributors/design-proposals/node/node-allocatable.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/contributors/design-proposals/node/node-allocatable.md b/contributors/design-proposals/node/node-allocatable.md index 09efa7a9..e4d3061a 100644 --- a/contributors/design-proposals/node/node-allocatable.md +++ b/contributors/design-proposals/node/node-allocatable.md @@ -295,7 +295,7 @@ The former disables Node Allocatable enforcement on all pods and the latter avoi This rollout in v1.6 might cause the following symptoms: 1. If `--kube-reserved` and/or `--system-reserved` flags are also specified, OOM kills of containers and/or evictions of pods. This can happen primarily to `Burstable` and `BestEffort` pods since they can no longer use up all the resource available on the node. -1. Total allocatable capadity in the cluster reduces resulting in pods staying `Pending` because Hard Eviction Thresholds are included in Node Allocatable. +1. Total allocatable capacity in the cluster reduces resulting in pods staying `Pending` because Hard Eviction Thresholds are included in Node Allocatable. ##### Proposed Timeline |