-
Epic
-
Resolution: Unresolved
-
Normal
-
None
-
None
-
cnv-adopt-rate-limits
-
CNV-10610 - Scale to 20k VMs
-
88% To Do, 13% In Progress, 0% Done
Goal
have a “dynamic” TuningPolicy that would follow kubelet, but not by default
User Stories
- As a cluster admin, I would like that the kubevirt rate limits folloiw the values I configure for kubelet, so that I don't have to care about the rate limits for kubevirt explicitly.
Non-Requirements
- List of things not included in this epic, to alleviate any doubt raised during the grooming process.
Notes
- It has to be ensured that this behavior is well documented.
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
-
CNV-14170 Manually adjust KubeVirt rate limiting by profile name
- Closed