-
Feature
-
Resolution: Unresolved
-
Undefined
-
None
-
None
-
None
Feature Overview:
Kruize, the recommendation engine for Resource Optimization for OpenShift, works with some fixed timeframes: 24-hour, 7-day, 15-day, based on 96-datapoints per 24-hour period (after Kruize 0.0.20: based on however many data points are available which fall in each period of time).
Since users know better their use case, we can help them by giving them some customization opportunities:
- Different time frames (eg. 10 days, 30 days, 90 days)
- Define relevant hours (eg. consider only data from 7am CST to 7pm CST Mon-Fri)
Goals:
- Let users define their own timeframes
- Let them do this at least per cluster. Bonus points if they can do this per namespace too.
Requirements:
- Requires enablement in Kruize and ros-ocp-backend
- Requires new settings in Settings and/or OpenShift cost model pages
Background and Strategic Fit:
Part of the Resource Optimization for OpenShift story.
Docs:
Docs will definitely be needed.
SMEs and Stakeholders:
| Name | Role |
| pgarciaq@redhat.com | PM |
| rbadagan@redhat.com rhn-support-kgaikwad rhn-support-lcouzens | Eng Manager |
| skukla@redhat.com | UX |
| dinogun21 | Architect |
- relates to
-
COST-6236 [Case 04058929] Enable different request and limits
-
- Backlog
-