Skip to content

Support better integration with “Stateful" schedulers #1517

Closed
@sidharta-s

Description

The current scheduler plugin implementation assumes that a scheduler “algorithm” needs to be used only when a pod needs to be scheduled (and not deleted/updated). It would be useful to generalize this with added support for letting the scheduler know about delete/update events as well. One example of where this would be very useful would be to integrate better with external/stateful schedulers/resource managers (e.g YARN). Instead of calling into the scheduler algorithm with a pod definition, maybe a pattern similar to what is used in the kubelet could be used ? ( “PodUpdate”/“PodOperation” ). Thoughts?

Metadata

Assignees

No one assigned

    Labels

    area/extensibilitypriority/awaiting-more-evidenceLowest priority. Possibly useful, but not yet enough support to actually get it done.sig/scalabilityCategorizes an issue or PR as relevant to SIG Scalability.sig/schedulingCategorizes an issue or PR as relevant to SIG Scheduling.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions