diff options
| author | xuhuilong <xuhuilong@ghostcloud.cn> | 2017-11-07 17:13:44 +0800 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2017-11-07 17:13:44 +0800 |
| commit | 3c4496a82724fb81119d473b5fb94fd93aa37bd1 (patch) | |
| tree | 971bb576a356ce47e038d5a7bc8fe68a05ce2422 /contributors/design-proposals/node/node-allocatable.md | |
| parent | 3ae089438e41922f45e0ef6c259e1674172ee873 (diff) | |
fix typos
Diffstat (limited to 'contributors/design-proposals/node/node-allocatable.md')
| -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 e4d3061a..a2d44f74 100644 --- a/contributors/design-proposals/node/node-allocatable.md +++ b/contributors/design-proposals/node/node-allocatable.md @@ -90,7 +90,7 @@ Together, evictions and node allocatable help improve node stability. As of v1.5, evictions are based on overall node usage relative to `Capacity`. Kubelet evicts pods based on QoS and user configured eviction thresholds. -More deails in [this doc](./kubelet-eviction.md#enforce-node-allocatable) +More details in [this doc](./kubelet-eviction.md#enforce-node-allocatable) From v1.6, if `Allocatable` is enforced by default across all pods on a node using cgroups, pods cannot exceed `Allocatable`. Memory and CPU limits are enforced using cgroups, but there exists no easy means to enforce storage limits though. |