-
Feature
-
Resolution: Unresolved
-
Normal
-
None
-
None
-
None
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?
- is related to
-
COST-5706 Resource Optimization for OpenShift
-
- In Progress
-