Epic Goal

Create a resource Optimization dashboard for ACM. This would be the ACM namespaces on the HUB to validate our requests are accurate, as well as our utilization of existing resources.

Why is this important?

This is the tool the user needs, to be able to manage the resource utilization and plan their capacity, both on day zero and day two.

Scenarios

• As a user I should be able to verify, articulate and track my Hub utilization.  Mainly if I am trending toward resource exhaustion (CPU or Memory)

  Acceptance Criteria

Dashboard is included in ACM grafana

Previous Work (Optional):

1. Resource Optimization dashboard

Open questions:

1. When looking at namespaces that the HUB uses (to make sure we are just tracking our utilization), will we be able to provide remaining resources?

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 - Doc issue opened with a completed template. Separate doc issue
  opened for any deprecation, removal, or any current known
  issue/troubleshooting removal from the doc, if applicable.