-
Story
-
Resolution: Won't Do
-
Normal
-
None
-
None
-
Upstream
-
2
-
False
-
None
-
False
-
OCPSTRAT-330 - [Upstream] OpenShift AutoScaler TechDebt (Phase 3)
-
-
-
CLOUD Ready for Development, CLOUD Sprint 244
User Story
As a developer I want a consistent way to manage the scale from zero annotations so that modifying this code is less brittle and easier to change across providers. Having a common module for this behavior will solve my problem.
Background
As part of converting our autoscaler to use the upstream scale from zero annotations, we need each provider to be using the common module from the MAO.
Steps
- Change internal references to the scale from zero annotations to use the module from MAO
- Update tests where necessary
Stakeholders
- openshift cloud team
Definition of Done
- AWS provider is using the MAO module
- Docs
- no docs changes should be required
- Testing
- updates where necessary
- is blocked by
-
OCPCLOUD-2146 Revert annotation carry patch for autoscaler
- To Do
-
OCPCLOUD-2138 Create scale from zero annotations util module in MAO
- Closed
- is cloned by
-
OCPCLOUD-2140 Update MAPI Azure MachineSet actuator to use scale from zero annotation module
- Closed
-
OCPCLOUD-2141 Update MAPI GCP MachineSet actuator to use scale from zero annotation module
- Closed
-
OCPCLOUD-2142 Update MAPI OpenStack MachineSet actuator to use scale from zero annotation module
- Closed
-
OCPCLOUD-2143 Update MAPI vSphere MachineSet actuator to use scale from zero annotation module
- Closed
-
OCPCLOUD-2144 Update MAPI Nutanix MachineSet actuator to use scale from zero annotation module
- Closed
-
OCPCLOUD-2145 Update MAPI IBMCloud MachineSet actuator to use scale from zero annotation module
- Closed
- links to