whentimeslows/website
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Merge master into release-1.10

Browse Source
This commit is contained in:
Andrew Chen
2018-03-16 16:29:38 -07:00
parent 39d6d27709 4ac2583637
commit a6fd58d42d
24 changed files with 341 additions and 42 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/concepts/policy/resource-quotas.md
+1 -1
View File
@@ -25,7 +25,7 @@ Resource quotas work like this:
status code `403 FORBIDDEN` with a message explaining the constraint that would have been violated.
- If quota is enabled in a namespace for compute resources like `cpu` and `memory`, users must specify
requests or limits for those values; otherwise, the quota system may reject pod creation. Hint: Use
the LimitRange admission controller to force defaults for pods that make no compute resource requirements.
the `LimitRanger` admission controller to force defaults for pods that make no compute resource requirements.
See the [walkthrough](/docs/tasks/administer-cluster/quota-memory-cpu-namespace/) for an example of how to avoid this problem.
Examples of policies that could be created using namespaces and quotas are: