-
Story
-
Resolution: Unresolved
-
Normal
-
None
-
None
-
Upstream
-
2
-
False
-
None
-
False
-
OCPSTRAT-330 - [Upstream] OpenShift AutoScaler TechDebt (Phase 3)
-
-
-
CLOUD Sprint 252, CLOUD Sprint 253, CLOUD Sprint 254, CLOUD Sprint 255, CLOUD Sprint 256, CLOUD Sprint 257, CLOUD Sprint 258, CLOUD Sprint 259, CLOUD Sprint 260, CLOUD Sprint 261, CLOUD Sprint 265, CLOUD Sprint 266, CLOUD Sprint 267
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
to help the transition to the upstream scale from zero annotations, we need to have the CAS recognize both sets of annotations, preferring the upstream, for at least one release cycle. this will allow us to have a window of deprecation on the old annotations.
Steps
- update CAS to recognize both annotations
- add a unit test to ensure prioritization works properly
Stakeholders
- openshift eng
Definition of Done
- CAS can recognize both sets of annotations
- Docs
- n/a
- Testing
- unit testing for priority behavior