-
Epic
-
Resolution: Unresolved
-
Normal
-
None
-
None
-
auto-kubevirt-rate-limit-metrics
-
False
-
-
False
-
To Do
-
CNV-12846 - Auto-Pilot Operator Level
-
100% To Do, 0% In Progress, 0% Done
-
---
-
---
Goal
The kubevirt api rate limit should be adjusted, if the cluster has the capacity to address a higher rate limit
User Stories
- As an admin of a huge and powerful cluster, I want that the kubevirt api rate limit adopts dynamically to the capacity of the cluster, so that I don't have to know about the kubevirt api rate limit.
Non-Requirements
- List of things not included in this epic, to alleviate any doubt raised during the grooming process.
Notes
- Any additional details or decisions made/needed
Done Checklist
| Who | What | Reference |
|---|---|---|
| DEV | Upstream roadmap issue (or individual upstream PRs) | <link to GitHub Issue> |
| DEV | Upstream documentation merged | <link to meaningful PR> |
| DEV | gap doc updated | <name sheet and cell> |
| DEV | Upgrade consideration | <link to upgrade-related test or design doc> |
| DEV | CEE/PX summary presentation | label epic with cee-training and add a <link to your support-facing preso> |
| 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> |
- relates to
-
-
- Closed
-