Bug 1459647 - [RFE] Min and Max Criteria for Replication Controllers
[RFE] Min and Max Criteria for Replication Controllers
Status: NEW
Product: OpenShift Container Platform
Classification: Red Hat
Component: RFE (Show other bugs)
3.5.1
All All
high Severity high
: ---
: ---
Assigned To: Eric Paris
Xiaoli Tian
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2017-06-07 13:15 EDT by Matthew Robson
Modified: 2017-06-07 13:27 EDT (History)
3 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 Matthew Robson 2017-06-07 13:15:17 EDT
3. What is the nature and description of the request?  
As an Openshift Administrator, I want to be able to specify a hard min (and max) for the number of PODs I expect to be available.  This would prevent a dc/rc from being scaled below or above the min/max for a particular application.

This is similar in nature to the min/max settings on the HPA.  In the HPA case, you are still able to scale below the min. After a period of time, it would be automatically scaled back up again.
  
4. Why does the customer need this? (List the business requirements here)  
This would allow developers to provide guidance on the min / max requirements their application needs and prevent it from being scaled outside of a desired operational range.

5. How would the customer like to achieve this? (List the functional requirements here)  
Adding a min/max option to the replication controller.

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

Can not scale below the min.
Can not scale above the max
  
7. Is there already an existing RFE upstream or in Red Hat Bugzilla?  
None found.

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.