<?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 CuraDevOps</title><link>https://curadevops.metacog.co.kr/tags/dra/</link><description>Recent content in Dra on CuraDevOps</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Fri, 04 Sep 2026 14:38:54 +0000</lastBuildDate><atom:link href="https://curadevops.metacog.co.kr/tags/dra/index.xml" rel="self" type="application/rss+xml"/><item><title>Kubernetes 1.37: DRA Extended Resource Support Reaches GA</title><link>https://curadevops.metacog.co.kr/insights/2026-09-04-kubernetes-v1-37-dra-updates/</link><pubDate>Fri, 04 Sep 2026 14:38:54 +0000</pubDate><guid>https://curadevops.metacog.co.kr/insights/2026-09-04-kubernetes-v1-37-dra-updates/</guid><description>&lt;ul>
&lt;li>&lt;strong>Platform/SRE — Plan:&lt;/strong> DRA Extended Resource support is now stable in 1.37, letting existing extended-resource workloads (e.g. example.com/gpu) route through DRA drivers without ResourceClaims or device plugins — a meaningful adoption path to evaluate this quarter. EOL for 1.37 is 2027-10-28, so no forced upgrade yet; plan an evaluation of DRA adoption for GPU/device workloads in the current planning cycle.&lt;/li>
&lt;li>&lt;strong>CI/CD — Skip&lt;/strong>&lt;/li>
&lt;li>&lt;strong>Leader — Learn:&lt;/strong> DRA reaching GA means GPU and accelerator workloads can now use a unified allocation model without dual plugin stacks — worth understanding for future platform architecture decisions around AI/ML infrastructure, but no toolchain strategy or budget action is required now.&lt;/li>
&lt;li>&lt;strong>Signals:&lt;/strong> Kubernetes 1.37 EOL 2027-10-28&lt;/li>
&lt;/ul></description></item></channel></rss>