Uploaded image for project: 'OpenShift Cloud'
  1. OpenShift Cloud
  2. OCPCLOUD-2493

Update CAO to add upstream scale from zero annotations

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Done
    • Icon: Normal Normal
    • openshift-4.16
    • 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

              raryan@redhat.com Rachel Ryan
              mimccune@redhat.com Michael McCune
              Huali Liu Huali Liu
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: