-
Story
-
Resolution: Unresolved
-
Normal
-
None
Goal
We would like to check if we should add Mem overcommit on usage calculations to the CNV dashboard to report on how to best size.
This is going to be shown on the customer facing dashboard.
Open questions
- is this going to fit the existing top consumer dashboard?
- how can we test it on QE side? how can we assume that the reported data are realistic? do we need automation? currently we don't have any infrastructure to test dashboard UI, can we do it only at API level?
Design document: https://docs.google.com/document/d/1ZCjre58MEEZ6XP5T2rMA4UgtnGajOcuEQZ560XSNCFo/edit?usp=sharing
Old Design document: https://docs.google.com/document/d/1TdZachO-9MZkYseRMutBO6SxQ40mYMCDUUbOWcyBu3s/edit?usp=sharing
Reference
https://issues.redhat.com/browse/CNV-44026
User Stories
- As a cluster Admin, I want to be able to monitor in the CNV dashboard on my cluster the Mem overcommit level so that I can eventually expand my cluster.
Notes
- https://issues.redhat.com/browse/CNV-14960 was at node level, this is an additional one at vm/namespace/cluster level.
- WASP is a temporary solution, we are not sure this will be compatible with the final implementation at k8s level
- incorporates
-
CNV-35106 Add a memory overcommit recording rule
-
- New
-