From f83e1741d79e18c0e2605a8c68b1a556e032e212 Mon Sep 17 00:00:00 2001 From: Sam Ghods Date: Fri, 22 Apr 2016 01:04:55 -0700 Subject: [PATCH] Update compute-resources.md Just some small suggestions. --- docs/user-guide/compute-resources.md | 11 +++++++---- 1 file changed, 7 insertions(+), 4 deletions(-) diff --git a/docs/user-guide/compute-resources.md b/docs/user-guide/compute-resources.md index 37ade2ec02..31ae7d9e98 100644 --- a/docs/user-guide/compute-resources.md +++ b/docs/user-guide/compute-resources.md @@ -22,13 +22,16 @@ server. ## Resource Requests and Limits of Pod and Container -Each container of a Pod can optionally specify `spec.container[].resources.limits.cpu` and/or -`spec.container[].resources.limits.memory` and/or `spec.container[].resources.requests.cpu` -and/or `spec.container[].resources.requests.memory`. +Each container of a pod can optionally specify one or more of the following: + +* `spec.container[].resources.limits.cpu` +* `spec.container[].resources.limits.memory` +* `spec.container[].resources.requests.cpu` +* `spec.container[].resources.requests.memory`. Specifying resource requests and/or limits is optional. In some clusters, unset limits or requests may be replaced with default values when a pod is created or updated. The default value depends on -how the cluster is configured. If value of requests is not specified, they are set to be equal +how the cluster is configured. If the `requests` values are not specified, they are set to be equal to limits by default. Please note that resource limits must be greater than or equal to resource requests.