Today we're going to demystify kube-scheduler and build a plugin!
The one talk I'm attending today (aside from, you know, my own) is "WASM + KWOK Wizardry: Writing and Testing Scheduler Plugins at Scale" by Dejan Pejchev & Jonathan Giannuzzi, G-Research. Because, uh, SimKube.
However, if you're looking for a talk to go to, I strongly recommend my friend @bizzybits's talk "Bring the Joy Back to Deployments!", in 250 AD!
Recall that you can make your pods (or whatever) to use a different/custom scheduler by setting a field in the podspec.
Ok we're all done.
But wait! In the title of the talk it says something about wasm.... when are we talking about wasm, exactly??
Any of y'all hiring new grads right now? I have a couple I've been working with who are fantastic and on the job market
Scheduler extenders became the scheduling framework, which is a set of pluggable APIs that are compiled directly into kube-scheduler -- lots more extension points. There are a number of in-tree plugins that you can use, but if you want to write your own you have to recompile kube-scheduler.
There's a new way to integrate plugins with the scheduling framework using wasm. WASM modules loaded at runtime via URL; it's in-process so no latency or cache issues. WASI-compatible languages (currently only Go).