Uploaded image for project: 'Cost Management'
  1. Cost Management
  2. COST-6472

Mark recommendations as "applied" or "stale"

XMLWordPrintable

    • False
    • Hide

      None

      Show
      None
    • False
    • COST-5706Resource Optimization for OpenShift
    • subs-cost

      Once customers apply a recommendation, we are still showing it as available, with wrong "current" values (we are still showing the old values). This is especially true for customers using COST-5689 (the RHDH plugin), where they can receive a recommendation in the plugin and apply immediately using an orchestrator workflow.

      We should have an API call to mark recommendations as "applied" and timestamp when it was applied.

      A "stale" status might also be a good idea in case a container is re-deployed with requests and limits different from what we recommend. But how to detect that? or should users the marking recommendations as stale for this or that container on this or that cluster/project/node as part of the CD workflow?

              Unassigned Unassigned
              pgarciaq@redhat.com Pau Garcia Quiles
              Anurag Patel, Preeti Wadhwani
              Votes:
              0 Vote for this issue
              Watchers:
              13 Start watching this issue

                Created:
                Updated: