Bug 1568519
Summary: | [RFE] Make pod limit per namespace configurable | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Chad Scribner <cscribne> |
Component: | RFE | Assignee: | Derek Carr <decarr> |
Status: | CLOSED WONTFIX | QA Contact: | Xiaoli Tian <xtian> |
Severity: | low | Docs Contact: | |
Priority: | medium | ||
Version: | 3.7.0 | CC: | aos-bugs, decarr, erich, jmalde, jokerman, mmccomas |
Target Milestone: | --- | ||
Target Release: | 3.10.z | ||
Hardware: | Unspecified | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2018-06-20 13:21:02 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: | |
Embargoed: |
Description
Chad Scribner
2018-04-17 16:45:17 UTC
Any update on this? I suspect that there are many large companies that would have a legitimate use case for this limit to be configurable. I am not sure I fully understand the request. It is possible today to quota 'pods' per namespace via ResourceQuota. For the customer scenario, isn't this just a matter of having the following: $ kubectl create quota foo --hard=pods=10 --namespace=x $ kubectl create quota foo --hard=pods=20 --namespace=y I suspect the customer is limiting per namespace pod usage today is via quota, but there is no need for the quota to be the same across each namespace. Closing this out. Per discussion with engineering, the 15k pod per namespace limit outlined in the docs is a soft/recommended limit but is not enforced in the OCP code. |