Bug 1376214

Summary: [DOCS] Limit Range documentation should explain better how limits work.
Product: OpenShift Container Platform Reporter: Ryan Howe <rhowe>
Component: DocumentationAssignee: Vikram Goyal <vigoyal>
Status: CLOSED EOL QA Contact: Vikram Goyal <vigoyal>
Severity: medium Docs Contact: Vikram Goyal <vigoyal>
Priority: unspecified    
Version: 3.3.0CC: aos-bugs, jokerman, mmccomas
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-08-10 06:46:00 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Ryan Howe 2016-09-14 21:45:50 UTC 
Document URL: https://docs.openshift.com/enterprise/latest/admin_guide/limits.html

Section Number and Name: 

Describe the issue: 
  The documentation needs to emphasize better how the limitranges work. The documentation can be leading in that setting a min and max means that your pod can use between this min and max amount of resources, this is incorrect.  

Suggestions for improvement: 

   If a container or pod requests a limit, or gets assigned a limit then that limit is the max amount of resources that a pod or container can consume.

   Setting a min and max just means that the pod or container can request setting a limit that falls in between those values but what ever limit it requests is the max amount of resources that a pod or container can consume.

   Real world examples would help. For example if I have this config in place here are a couple scenarios you would see. 


Additional information: 

See bug 1358497 for more information. 

https://bugzilla.redhat.com/show_bug.cgi?id=1358497#c11