<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Node-Swap on CuraDevOps</title><link>https://curadevops.metacog.co.kr/tags/node-swap/</link><description>Recent content in Node-Swap on CuraDevOps</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Mon, 05 Oct 2026 19:28:00 +0000</lastBuildDate><atom:link href="https://curadevops.metacog.co.kr/tags/node-swap/index.xml" rel="self" type="application/rss+xml"/><item><title>Kubernetes Node Swap Hits GA in v1.34, Up to 3× Pod Density Gain</title><link>https://curadevops.metacog.co.kr/insights/2026-10-05-scaling-kubernetes-workloads-with-node-swap/</link><pubDate>Mon, 05 Oct 2026 19:28:00 +0000</pubDate><guid>https://curadevops.metacog.co.kr/insights/2026-10-05-scaling-kubernetes-workloads-with-node-swap/</guid><description>&lt;ul>
&lt;li>&lt;strong>Platform/SRE — Plan:&lt;/strong> Kubernetes v1.34 GA swap support with NVMe backing is worth evaluating for memory-dense node pools this quarter; assess enabling swap on nodes running agentic AI or sandboxed workloads to reduce OOM kills and improve pod density without fleet-wide urgency.&lt;/li>
&lt;li>&lt;strong>CI/CD — Learn:&lt;/strong> The benchmark covers CI/CD kernel build workloads as a validated use case, but enabling swap on nodes is a platform configuration decision — useful context for understanding build pod resource headroom if your CI runs on shared Kubernetes clusters.&lt;/li>
&lt;li>&lt;strong>Leader — Plan:&lt;/strong> Up to 3× pod density on existing hardware is a material FinOps opportunity worth adding to the next infrastructure planning cycle; evaluate whether adopting Kubernetes v1.34 swap + NVMe changes the cost model for memory-intensive AI and build workloads in your standard platform stack.&lt;/li>
&lt;li>&lt;strong>Signals:&lt;/strong> GA announcement&lt;/li>
&lt;/ul></description></item></channel></rss>