-
Feature
-
Resolution: Unresolved
-
Major
-
None
-
None
-
Upstream
-
False
-
0% To Do, 40% In Progress, 60% Done
-
0
-
Program Call
Feature Overview
This is a TechDebt and doesn't impact OpenShift Users.
As the autoscaler has become a key feature of OpenShift, there is the requirement to continue to expand it's use bringing all the features to all the cloud platforms and contributing to the community upstream. This feature is to track the initiatives associated with the Autoscaler in OpenShift.
Goals
- Scale from zero available on all cloud providers (where available)
- Required upstream work
- Work needed as a result of rebase to new kubernetes version
Requirements
| Requirement | Notes | isMvp? |
|---|---|---|
| vSphere autoscaling from zero | No | |
| Upstream E2E testing | No | |
| Upstream adapt scale from zero replicas | No | |
Out of Scope
n/a
Background, and strategic fit
Autoscaling is a key benefit of the Machine API and should be made available on all providers
Assumptions
Customer Considerations
Documentation Considerations
- Target audience: cluster admins
- Updated content: update docs to mention any change to where the features are available.
- clones
-
-
- Closed
-
- links to
[OCPSTRAT-330] [Upstream] OpenShift AutoScaler TechDebt (Phase 3)
jrouth@redhat.com afaik, we have documented all the pieces that were originally meant to be contributed to upstream. there is some documentation that i think we should add(e.g. a discussion of scale from zero annotations), but it's not a blocker for this card.
Michael McCune
added a comment - - edited jrouth@redhat.com afaik, we have documented all the pieces that were originally meant to be contributed to upstream. there is some documentation that i think we should add(e.g. a discussion of scale from zero annotations), but it's not a blocker for this card. 
Feature Analysis Color: Green
Estimated Completion Date: 2024-08-30
Work Remaining: Cluster Infrastructure (4)