Uploaded image for project: 'Managed Service - API'
  1. Managed Service - API
  2. MGDAPI-5030

Consume 3scale build and update RHOAM 3scale reconcile logic

    XMLWordPrintable

Details

    • Task
    • Resolution: Duplicate
    • Major
    • None
    • None
    • None
    • None

    Description

      WHAT
      Once the 3scale build with the changes are available, RHOAM should be updated to use this build.
      Additionally, the APIManager CR should be updated to use the new optional fields to reduce the logic performed by RHOAM. The RHOAM 3scale reconciler should be updated to remove any redundant logic from comsuming the new 3scale operator with the suggested changes

      HOW

      • APManager CR updated to use new fields
      • Redundant logic from RHOAM 3scale reconciler removed

      TESTS
      <List of related tests>

      DONE

      • RHOAM installation succeeds
      • E2E tests are successfull
      • Upgrade from previous release to new release is successfull

      Attachments

        Issue Links

          is blocked by

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) THREESCALE-6735 Reconcile secrets - customPolicies

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) THREESCALE-8997 Allow defining the pod priority of components via APIManager CR

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) THREESCALE-8999 Allow adding labels to components via APIManager CR

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) THREESCALE-9000 Allow adding annotations to components via APIManager CR

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) THREESCALE-9001 Re-sync routes when namespace is deleted for restoration

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Closed

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) THREESCALE-8998 Allow defining zone topology spread constraints for components via APIManager CR

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • To Test For On-Prem

          Activity

            People

              Unassigned Unassigned
              chfan@redhat.com Kevin Chi Keen Fan
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: