Epic Goal

Provide namespace / application limits/request types of recommendations based on usage from my actual running workloads.

I need to provide recommendations using existing data collected, and provide the recommendations experience based on 7d/14d/28d range in my data-sample.

Why is this important?

Customers need to reduce wasted resources and implement cost saving strategies.

Scenarios

1. As a platform engineer responsible for multiple clusters, I need to be able to view the recommendations from across the fleet of clusters that I manage.
2. As a platform engineer responsible for multiple clusters, I want to be able to view namespace level recommendations based on pod/container metrics that I've collected from my managed fleet.
3. As a platform engineer responsible for multiple clusters, I want to be able to have an output report of some kind, CSV perhaps, that allows me to easily share this information with app-dev teams.

Acceptance Criteria

Deliver an operator that can run alongside the ACM hub.

Running alongside the ACM hub, make use of the ACM observability Thanos data.

Provide visualization of recommendation with a small historical view of the data with the proposed new limit settings.

Dependencies (internal and external)

1. Recommendations will be based of Kruize https://github.com/kruize/kruize

Previous Work (Optional):

Recommendations will be based of Kruize https://github.com/kruize/kruize

Open questions:

1. …

Done Checklist

• CI - CI is running, tests are automated and merged.
• Release Enablement <link to Feature Enablement Presentation>
• DEV - Upstream code and tests merged: <link to meaningful PR or GitHub
  Issue>
• DEV - Upstream documentation merged: <link to meaningful PR or GitHub
  Issue>
• DEV - Downstream build attached to advisory: <link to errata>
• QE - Test plans in Polarion: <link or reference to Polarion>
• QE - Automated tests merged: <link or reference to automated tests>
• DOC - Downstream documentation merged: <link to meaningful PR>

 ----

ACM Epic Done Checklist

See presentation and details.

Update with "Y" if Epic meets the requirement, "N" if it does not,  or "N/A" if not applicable.

• _ FIPS Readiness
• _ Works in Disconnected
• _ Global Proxy Support
• _ Installable to Infrastructure Nodes
• _ No impacts to Performance and Scalability
• _ Backup and Restorable