<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Kind on Anish Bista</title><link>https://anishbista.org/tags/kind/</link><description>Recent content in Kind on Anish Bista</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Wed, 28 Oct 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://anishbista.org/tags/kind/index.xml" rel="self" type="application/rss+xml"/><item><title>Your Scheduler Can Finally See Your GPUs: Kubernetes DRA</title><link>https://anishbista.org/blog/dynamic-resource-allocation-dra-on-kind/</link><pubDate>Wed, 28 Oct 2026 00:00:00 +0000</pubDate><guid>https://anishbista.org/blog/dynamic-resource-allocation-dra-on-kind/</guid><description>&lt;blockquote>
&lt;p>&lt;strong>Note:&lt;/strong> A big shout-out to the Kubernetes upstream community, especially WG Device Management, SIG Node and SIG Scheduling, who spent years taking DRA from an idea to a GA feature. Everything in this post is built on their work. Thank you!&lt;/p>&lt;/blockquote>
&lt;p>Your node has 8 GPUs. A pod asks for &lt;code>nvidia.com/gpu: 1&lt;/code>. Which GPU does it get? How much memory does that GPU have? Can another pod share it? With device plugins, Kubernetes can&amp;rsquo;t answer any of these: the scheduler only sees a number, &lt;code>8&lt;/code>, and the kubelet picks a card at the last moment. &lt;strong>Dynamic Resource Allocation (DRA)&lt;/strong> fixes that. The scheduler sees every device with its model and memory, and a pod says exactly what it needs. DRA has been GA since Kubernetes v1.34, so it&amp;rsquo;s already switched on in your cluster.&lt;/p></description></item></channel></rss>