<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Kube-Scheduler on Project Wintermute</title><link>https://wintermutecore.com/tags/kube-scheduler/</link><description>Recent content in Kube-Scheduler on Project Wintermute</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sat, 18 Jul 2026 14:00:02 +0000</lastBuildDate><atom:link href="https://wintermutecore.com/tags/kube-scheduler/index.xml" rel="self" type="application/rss+xml"/><item><title>kube-scheduler CompositePodGroup API Notes For Batch Platforms</title><link>https://wintermutecore.com/posts/kube-scheduler-composite-podgroup-api-notes/</link><pubDate>Sat, 18 Jul 2026 14:00:02 +0000</pubDate><guid>https://wintermutecore.com/posts/kube-scheduler-composite-podgroup-api-notes/</guid><description>&lt;p&gt;Recent activity in &lt;a href="https://github.com/kubernetes/kube-scheduler"&gt;kubernetes/kube-scheduler&lt;/a&gt; is small by commit count, but it changes scheduler framework contracts around gang scheduling. The useful bit for data platform operators is not a new flag; it is the API surface that lets plugins reason about CompositePodGroup state as a first class queue entity.&lt;/p&gt;</description></item></channel></rss>