Bug 1473686 - [RFE] set pods-per-core to 0 and allow users to set a value that would cover their needs
[RFE] set pods-per-core to 0 and allow users to set a value that would cover ...
Status: NEW
Product: OpenShift Container Platform
Classification: Red Hat
Component: Kubernetes (Show other bugs)
3.5.0
Unspecified Unspecified
unspecified Severity low
: ---
: ---
Assigned To: Derek Carr
DeShuai Ma
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2017-07-21 08:27 EDT by Sergi Jimenez Romero
Modified: 2017-07-21 11:17 EDT (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Sergi Jimenez Romero 2017-07-21 08:27:43 EDT
From the RFE template:

> 3. What is the nature and description of the request?  

Default value of pods-per-core has been set to 10, which might or not fit all OpenShift installations out there.

> 4. Why does the customer need this? (List the business requirements here)  

During the upgrade of their platform, they found out that the number of pods they could run on their nodes, was lowered down due the pods-per-core being set to 10.

> 5. How would the customer like to achieve this? (List the functional requirements here)  

Setting pods-per-core to 0 to allow customers/users to set it to their own needs.

> 6. For each functional requirement listed, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented.  

Making a new installation or an upgrade (from a version where pods-per-core wasn't set to 10) and check the number of pods that are allowed to run.

> 10. List any affected packages or components.
Kubernetes

Note You need to log in before you can comment on or make changes to this bug.