Modelplane v0.2: more clouds, and traffic you can direct

Modelplane released v0.2 of its open-source inference orchestration platform, adding support for Nebius and Azure AKS cloud providers, weighted request routing for canarying and traffic splitting, and cluster taints for capacity reservation and draining. The update aims to unify models, engines, clouds, and accelerators into a single controllable system, building on the project's initial launch three weeks ago.

Modelplane v0.2 is out. We open sourced the project three weeks ago, and since then we've had a lot of traction and some great discussions with people running inference. The mission driving each release is the same: Modelplane brings together the models, engines, clouds, and accelerators that make up the intelligence ecosystem so you can operate them as a single system under your control. And we are building this in the open. This release adds two more cloud providers, weighted request routing, and cluster taints for reserving and draining capacity. Here's what's new. More providers more-providers At launch, Modelplane provisioned inference clusters on GKE and EKS, or ran on any Kubernetes you brought yourself. v0.2 adds two more providers, Nebius https://nebius.com and Azure AKS https://azure.microsoft.com/en-us/products/kubernetes-service . A Nebius cluster is about as much YAML as it sounds like it should be. You name it, point it at Nebius, and Modelplane provisions the rest from the credentials you already configured: Both work the same way as GKE: an InferenceClass describes the hardware, an InferenceCluster provisions it, and the same nodePools model applies. On GKE, the GPU node pools Modelplane creates now cold-start from zero, so an idle pool stops billing you when nothing is running on it. You can also still bring your own cluster on any Kubernetes, on any cloud or on-prem, for providers Modelplane doesn't provision yet. If you want a provisioner for a particular cloud, upvote or open an issue https://github.com/modelplaneai/modelplane/issues . Weighted routing weighted-routing A ModelService can now split traffic across its endpoints by weight: Weights are relative, and an endpoint with no weight defaults to 1. The endpoint stays fixed while you change the split, which covers canarying a new model version, shifting traffic between two deployments, and splitting between a hosted provider and your own deployment. Weights are the first step here, and there's a lot more routing functionality on the way. Taints and draining clusters taints-and-draining-clusters v0.2 also lets you decide which clusters take work, using the same taints and tolerations that Kubernetes already uses for nodes, lifted up to the cluster. You taint an InferenceCluster , and only models that tolerate the taint will schedule onto it: This is useful for keeping a sovereign cluster, or one with scarce hardware, for the workloads that need it. A deployment opts in with a matching toleration under its template: The same mechanism drains a cluster. Taint it with NoExecute instead of NoSchedule and Modelplane moves the running replicas off onto other clusters in the fleet, so you can take a cluster out for maintenance without hand-migrating what's on it. Remove the taint and it takes work again. The full release notes are on GitHub https://github.com/modelplaneai/modelplane/releases/tag/v0.2.0 , and the getting-started guide https://docs.modelplane.ai/getting-started/ now covers deploying on AKS and Nebius. Questions and feedback are welcome in Slack https://slack.modelplane.ai .