Re: [kubernetes/kubernetes] Try to make scheduler volume binding more extendable (#56180)
Michelle Au
/assign @msau42 @bsalamat
/cc @liggitt
—
You are receiving this because you are on a team that was mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
Michelle Au
Is this a BUG REPORT or FEATURE REQUEST?:
@kubernetes/sig-storage-feature-requests
@kubernetes/sig-scheduling-feature-requests
What happened:
Before volume scheduling moves to beta, see if there's a way to make the volume binding changes more pluggable to:
- better support custom schedulers
- make it easier for other cluster-level resources to integrate into the pod scheduling flow
fejta-bot
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale
Michelle Au
/remove-lifecycle stale
fejta-bot
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale
—
Michelle Au
/remove-lifecycle stale
fejta-bot
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale
—
Michelle Au
/remove-lifecycle stale
fejta-bot
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale
—
Michelle Au
/remove-lifecycle stale
/lifecycle frozen
Michelle Au
It looks like scheduler has started implement plugin hooks for the scheduler v2 framework. @cofyc can you look into refactoring the volume scheduling code to use the new framework?
Yecheng Fu
sure
/assign
bsalamat
Thanks, @msau42 and @cofyc for taking initiative here. While we encourage you to take a look at the extension points and think about converting the volume scheduling code to plugins, please do not rely on the plugin interface yet. We plan to have the alpha available in 1.14, which means that the interface is currently in pre-alpha phase and will most probably change in the next couple of months.
Michelle Au
Thanks for the clarification Bobby! I think we can still at least prototype and help find issues since volume scheduling is one of the more complicated plugins.
Yecheng Fu
Design (Draft)
Filter
Implement scheduler filter plugin in which we call FindPodVolumes to find all feasible nodes and save pre-bound PVs and pre-provisioned PVCs in pod binding cache.
Reserve
Implement scheduler reserve plugin in which we call AssumePodVolumes to assume pre-bound PVs and pre-provisioned PVCs of selected node.
Pre-bind
Implement scheduler pre-bind plugin in which we call BindPodVolumes to bind pre-bound PVs and provision pre-provisioned PVCs.
If successfully, continue to bind pod.
If failed, exit scheduling cycle with non-unscheduable error.
Clean pod binding cache
When pod is removed from scheduling queue
References
- https://github.com/kubernetes/community/blob/master/contributors/design-proposals/scheduling/scheduling-framework.md
- kubernetes/community#3082
Yecheng Fu
another issue is how to pass KubeSchedulerConfiguration.BindTimeoutSeconds to volume binder plugin.
Kubernetes Prow Robot
—
You are receiving this because you are on a team that was mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.