Repository navigation
scheduler-perf: inline createPods inside createPodGroups and createPodGroups inside createCompositePodGroups. #143281
Description
What would you like to be added?
/sig scheduling
/kind cleanup
/wg workload-aware-scheduling
As per discussion: #141706 (comment)
createCompositePodGroups propagates multiple fields/params to createPodGroups which require when creating hierarchies for scheduler-perf tests. Similarly createPodGroups also propagate its PodGroup count to createPods.
Better cleanup would be, to inline createPods inside createPodGroups and also inline createPodGroups inside createCompositePodGroups when it comes to CompositePodGroup cases or standalone PodGroups.
Why this is needed?
This improves test cases configurations, and their readability, and reduces usage of parameters.
Activity
[-]scheduler-perf: inline createPods inside createPodGroups, and createPodGroups inside createCompositePodGroups.[/-][+]scheduler-perf: inline createPods inside createPodGroups and createPodGroups inside createCompositePodGroups.[/+]kubernetes-prow commentedon Oct 21, 2026
This issue is currently awaiting triage.
If a SIG or subproject determines this is a relevant issue, they will accept it by applying the
triage/acceptedlabel and provide further guidance.The
triage/acceptedlabel can be added by org members by writing/triage acceptedin a comment.Details
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.
yashaggarwal85d commentedon Oct 25, 2026
Hi @iomarsayed, are you planning to do this one yourself? If not I'd like to take it. I have a version ready where createCompositePodGroups takes a nested
podGroupsand createPodGroups takes a nestedpodspluspodsPerGroup, socountMultiplierParamand the$podGroupsCount/$parentLevelparams go away. Happy to change the shape if you and @dom4ha had something else in mind.