From 43d291131bc9bd0f05761a5a65c3e790e9a39b7e Mon Sep 17 00:00:00 2001 From: huzhengchuan Date: Fri, 6 Oct 2017 20:51:30 +0800 Subject: Fix typos --- contributors/design-proposals/node/node-allocatable.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'contributors/design-proposals/node/node-allocatable.md') 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 -- cgit v1.2.3