feat(podgrouper): support owner-chain fallback for plugin selection #885
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
feat(podgrouper): Implement owner-reference chain fallback for plugin selection
Enhance
PodGrouper.GetPGMetadata()to iterate through the owner chain (allOwnersslice)from top-most owner down, selecting the highest GVK with a non-default plugin via
PluginsHub.GetPodGrouperPlugin(). Eliminates scheduling regressions when new owner typesgain RBAC visibility but lack dedicated plugins (e.g., JobSet → fallback to
batch/v1.Job).Related Issues
Fixes #856
Checklist
Breaking Changes
None
Additional Notes
Before:
JobSet → no plugin → defaultgrouper(per-pod grouping)After:
JobSet → no plugin → Job → job.NewK8sJobGrouper(Job-level grouping)Implementation via
selectPluginForOwners()helper usingDefaultPluginsHubtype assertion.No
PluginsHubinterface or plugin signature changes required.