Let's use the Harness UI as a source of inspiration to solve some of our missing features or controversial UI decisions:

https://developer.harness.io/docs/cloud-cost-management/use-ccm-cost-optimization/ccm-recommendations/workload-recommendations/

Feature Overview:{}

[ ] Must Technical work: multiple replicas for scalability, high-availability, etc

[ ] Must Technical work: bulk upload of data from ros-ocp-backend to Kruize to avoid multiple updates

[ ] Must Technical work: data deduplication between Kruize and ROS OCP

[ ] Must: show the current CPU and RAM usage values, as box plots where the user can see the minimum, maximum, average, outliers, etc for that day. The Harness UI looks like a source of inspiration.

[ ] Must: show delta as a percentage, not a value. This helps the user better and removes the problem of what units to use.

[ ] Must: show current and recommended values as a YAML file with the very units the user has configured in their configuration files. Harness' UI is a good source of inspiration.

[ ] Should: have profile-based recommendations, not just time-based recommendations. The Harness UI is a good source of inspiration.

[-] Should: in the OpenShift page, in the Projects perspective, show an indication that there’s optimization opportunities. Implemented but currently fails sometimes because of different API calls.

[ ] Should: in the Overview > Top Projects section, show how many optimization opportunities a project has (it's already in OpenShift > Projects)

[ ] Should: be able to export the recommendations, both from the Optimizations page and from the OpenShift > Project > Resource Optimization tab

[ ] Should: have sortable columns in the OpenShift page (requires same API) (i. e. I want to be able to sort by number of optimizations)

[ ] Could: have type ahead in Optimizations page

Docs:

Yes

SMEs and Stakeholders: