diff options
| author | Kubernetes Submit Queue <k8s-merge-robot@users.noreply.github.com> | 2016-11-28 11:43:26 -0800 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2016-11-28 11:43:26 -0800 |
| commit | 4905d26566770f157276e8a09b81bfabebf742ac (patch) | |
| tree | ecf276854440253374849a6a5790d2a2382f43d7 | |
| parent | 53bd6400c2484cfcace52d12e7f2370a729f7bc7 (diff) | |
| parent | 09d8fabb877b2bbaddac6ec4317c418b5ea035f7 (diff) | |
Merge pull request #36975 from xiangpengzhao/fix-design-doc
Automatic merge from submit-queue
Fix container to pod in resource-qos.md
`...then the container is classified as Guaranteed.`
Here `container` should be `pod`.
| -rw-r--r-- | resource-qos.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/resource-qos.md b/resource-qos.md index b6feaae5..cfbe4faf 100644 --- a/resource-qos.md +++ b/resource-qos.md @@ -51,7 +51,7 @@ The relationship between "Requests and Limits" and "QoS Classes" is subtle. Theo Pods can be of one of 3 different classes: -- If `limits` and optionally `requests` (not equal to `0`) are set for all resources across all containers and they are *equal*, then the container is classified as **Guaranteed**. +- If `limits` and optionally `requests` (not equal to `0`) are set for all resources across all containers and they are *equal*, then the pod is classified as **Guaranteed**. Examples: |