From d0081d3c6e0d8f5ea684dc80b09c4e81ce1e5aa2 Mon Sep 17 00:00:00 2001 From: Sam Ghods Date: Fri, 22 Apr 2016 01:05:56 -0700 Subject: [PATCH] Update compute-resources.md --- docs/user-guide/compute-resources.md | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/docs/user-guide/compute-resources.md b/docs/user-guide/compute-resources.md index 31ae7d9e98..dd1828d803 100644 --- a/docs/user-guide/compute-resources.md +++ b/docs/user-guide/compute-resources.md @@ -31,9 +31,8 @@ Each container of a pod can optionally specify one or more of the following: 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 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. +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 limits must always be greater than or equal to requests. Although requests/limits can only be specified on individual containers, it is convenient to talk about pod resource requests/limits. A *pod resource request/limit* for a particular resource