-
Story
-
Resolution: Done
-
Normal
-
None
-
Upstream
-
2
-
False
-
None
-
False
-
OCPSTRAT-330 - [Upstream] OpenShift AutoScaler TechDebt (Phase 3)
-
-
-
CLOUD Sprint 249, CLOUD Sprint 250, CLOUD Sprint 251, CLOUD Sprint 252, CLOUD Sprint 253
User Story
As a developer, in order to deprecate the old annotations, we will need to carry both for at least one release cycle. Updating the CAO to apply the upstream annotations, and the CAS to accept both (preferring upstream), will allow me to properly deprecate the old annotations.
Background
During the process of making the CAO recognize the annotations, we need to enable it to modify the machineset to have the new annotation. Similarly, we want the autoscaler to recognize both sets of annotations in the short term while we switch.
Steps
- update CAO to enable annotations
- write unit tests
Stakeholders
- openshift cloud team
Definition of Done
- CAO applies upstream annotations, leaves old annotations alone
- Docs
- upstream annotations referenced in product docs
- Testing
- unit testing of behavior
- blocks
-
OCPCLOUD-2501 Add e2e tests to ensure that CAO is adding the proper annotations
- Closed
- links to
(1 links to)
1.
|
Post-merge Testing | Closed | Huali Liu | ||
2.
|
E2E Automation | Closed | Huali Liu |