<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Modelplane on SREKubeCraft | Nick Nikolakakis</title><link>https://srekubecraft.io/tags/modelplane/</link><description>Recent content in Modelplane on SREKubeCraft | Nick Nikolakakis</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sun, 30 Aug 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://srekubecraft.io/tags/modelplane/index.xml" rel="self" type="application/rss+xml"/><item><title>Modelplane - Fleet Inference Across Clusters, Demoed Without a Single GPU</title><link>https://srekubecraft.io/posts/modelplane-fleet-inference/</link><pubDate>Sun, 30 Aug 2026 00:00:00 +0000</pubDate><guid>https://srekubecraft.io/posts/modelplane-fleet-inference/</guid><description>&lt;p&gt;Serving one model on one cluster is a solved problem. Pick an engine, hand it a GPU, point traffic at it. I have written about that path twice already, with &lt;a href="https://srekubecraft.io/posts/kserve/"&gt;KServe&lt;/a&gt; and with &lt;a href="https://srekubecraft.io/posts/llm-d-distributed-inference/"&gt;llm-d&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;The version nobody has solved cleanly is the fleet. GPUs are scarce, so you take capacity wherever you can get it: some on EKS, some on GKE, a reserved block in a neocloud, a rack you already own. Now you have five clusters that each need the identical serving stack, and a permanent matchmaking problem deciding which model runs on which hardware in which region. Underneath that sit two different jobs that most platforms blur together: the platform team&amp;rsquo;s job of publishing what hardware exists, and the ML team&amp;rsquo;s job of asking for the hardware they need.&lt;/p&gt;</description></item></channel></rss>