-
Epic
-
Resolution: Done
-
Major
-
None
-
None
-
cnv-altert
-
False
-
-
False
-
To Do
-
0% To Do, 0% In Progress, 100% Done
-
---
-
---
Goal
If a single node contains more than 50 images, pod scheduling might be imbalanced across nodes. Let's report back to telemetry that this happend.
User Stories
- As a Red Hat, I want know how often there are imbalanced nodes, so that I can decide how many customers are impacted.
Non-Requirements
- List of things not included in this epic, to alleviate any doubt raised during the grooming process.
Notes
- This is because the list of images on a node is shortened to 50 by default. You can disable the image limit by editing the KubeletConfig object and setting the value of nodeStatusMaxImages to -1.
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> |
