diff options
| author | Haoran Wang <haowang@redhat.com> | 2017-02-24 09:14:28 +0800 |
|---|---|---|
| committer | Haoran Wang <haowang@redhat.com> | 2017-02-24 09:14:28 +0800 |
| commit | e0cf34381e0842addf590bc43e62d669c25164ed (patch) | |
| tree | 42abda89df11d29d1e30273712042b1f1e778843 | |
| parent | cb54588b4236f7b4860fc39cd256326a30ce88ba (diff) | |
fix typo
| -rw-r--r-- | contributors/design-proposals/node-allocatable.md | 2 | ||||
| -rw-r--r-- | contributors/design-proposals/resource-qos.md | 2 | ||||
| -rw-r--r-- | contributors/design-proposals/resources.md | 4 |
3 files changed, 4 insertions, 4 deletions
diff --git a/contributors/design-proposals/node-allocatable.md b/contributors/design-proposals/node-allocatable.md index 3dec408a..09efa7a9 100644 --- a/contributors/design-proposals/node-allocatable.md +++ b/contributors/design-proposals/node-allocatable.md @@ -326,7 +326,7 @@ for overflow and the node should continue to function. If the node has been sche situation. A recommended alternative is to enforce KubeReserved once Kubelet supports it (Phase 2). -In the [future](#future-work) we may set a parent cgroup for kubernetes components, with limits set +In the future we may set a parent cgroup for kubernetes components, with limits set according to `KubeReserved`. ### 3rd party schedulers diff --git a/contributors/design-proposals/resource-qos.md b/contributors/design-proposals/resource-qos.md index 7c84e778..55962158 100644 --- a/contributors/design-proposals/resource-qos.md +++ b/contributors/design-proposals/resource-qos.md @@ -20,7 +20,7 @@ Borg increased utilization by about 20% when it started allowing use of such non ## Requests and Limits -For each resource, containers can specify a resource request and limit, `0 <= request <= `[`Node Allocatable`](../proposals/node-allocatable.md) & `request <= limit <= Infinity`. +For each resource, containers can specify a resource request and limit, `0 <= request <= `[`Node Allocatable`](../design-proposals/node-allocatable.md) & `request <= limit <= Infinity`. If a pod is successfully scheduled, the container is guaranteed the amount of resources requested. Scheduling is based on `requests` and not `limits`. The pods and its containers will not be allowed to exceed the specified limit. diff --git a/contributors/design-proposals/resources.md b/contributors/design-proposals/resources.md index bb66885b..6b01dbeb 100644 --- a/contributors/design-proposals/resources.md +++ b/contributors/design-proposals/resources.md @@ -302,8 +302,8 @@ where a `<CPU-info>` or `<memory-info>` structure looks like this: ```yaml { mean: <value> # arithmetic mean - max: <value> # minimum value - min: <value> # maximum value + max: <value> # maximum value + min: <value> # minimum value count: <value> # number of data points percentiles: [ # map from %iles to values "10": <10th-percentile-value>, |