<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Dra on Under the Model</title><link>https://oguzpastirmaci.com/tags/dra/</link><description>Recent content in Dra on Under the Model</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Mon, 26 Oct 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://oguzpastirmaci.com/tags/dra/index.xml" rel="self" type="application/rss+xml"/><item><title>Gang Scheduling and Topology-Aware Scheduling in Upstream Kubernetes</title><link>https://oguzpastirmaci.com/posts/gang-scheduling-and-topology-aware-scheduling-in-upstream-kubernetes/</link><pubDate>Mon, 26 Oct 2026 00:00:00 +0000</pubDate><guid>https://oguzpastirmaci.com/posts/gang-scheduling-and-topology-aware-scheduling-in-upstream-kubernetes/</guid><description>&lt;p&gt;In my &lt;a href="https://oguzpastirmaci.com/posts/rdma-network-locality-for-multi-node-jobs-with-kueue/"&gt;Kueue post&lt;/a&gt;, Kueue did all the placement work. It kept the pods of a job in one RDMA local block or network block. It started a job only when all of its pods fit. The default scheduler only bound each pod to the node that Kueue picked.&lt;/p&gt;&#10;&lt;p&gt;This is changing. In v1.35, kube-scheduler got an alpha feature that schedules a group of pods as one unit. In v1.36, another alpha feature started to keep a group in one topology domain. The work comes from the &lt;a href="https://github.com/kubernetes/community/blob/c189d23894d0eb65b92853052e72f7b242d62516/wg-workload-aware-scheduling/charter.md"&gt;Workload-Aware Scheduling working group&lt;/a&gt; of SIG Scheduling.&lt;/p&gt;</description></item></channel></rss>