<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Dynamic-Resource-Allocation on CuraDevOps</title><link>https://curadevops.metacog.co.kr/tags/dynamic-resource-allocation/</link><description>Recent content in Dynamic-Resource-Allocation on CuraDevOps</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Fri, 07 Aug 2026 11:39:24 +0000</lastBuildDate><atom:link href="https://curadevops.metacog.co.kr/tags/dynamic-resource-allocation/index.xml" rel="self" type="application/rss+xml"/><item><title>Kubernetes DRA vs HAMi: GPU Sharing Architecture Compared</title><link>https://curadevops.metacog.co.kr/insights/2026-08-07-does-kubernetes-dra-replace-hami/</link><pubDate>Fri, 07 Aug 2026 11:39:24 +0000</pubDate><guid>https://curadevops.metacog.co.kr/insights/2026-08-07-does-kubernetes-dra-replace-hami/</guid><description>&lt;ul>
&lt;li>&lt;strong>Platform/SRE — Learn:&lt;/strong> Useful framing for platform engineers managing GPU workloads on Kubernetes — DRA changes the device-allocation model relative to legacy device plugins and HAMi. No deprecation date or migration deadline exists in the signals, so no action is required now.&lt;/li>
&lt;li>&lt;strong>CI/CD — Skip&lt;/strong>&lt;/li>
&lt;li>&lt;strong>Leader — Learn:&lt;/strong> If the org is building or standardizing an AI/GPU platform on Kubernetes, this comparison informs the build-vs-adopt decision between DRA and HAMi; no strategic urgency exists without a concrete deadline or licensing change.&lt;/li>
&lt;/ul></description></item></channel></rss>