diff options
| author | Kubernetes Submit Queue <k8s-merge-robot@users.noreply.github.com> | 2017-11-07 18:40:58 -0800 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2017-11-07 18:40:58 -0800 |
| commit | 332d15fa0dcf31bd32e9bfaf5aa02723e9e5b686 (patch) | |
| tree | be006aaaa8d771a3eda9777e12cf74baadb7865d /contributors | |
| parent | 0bad012e24eddb0811dd2c471c93fbe9fcad0bde (diff) | |
| parent | 3c4496a82724fb81119d473b5fb94fd93aa37bd1 (diff) | |
Merge pull request #1359 from xuhuilong/patch-3
Automatic merge from submit-queue.
fix typo
Diffstat (limited to 'contributors')
| -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. |