Mirantis has rolled out MOSK 26.1, the latest version of Mirantis OpenStack for Kubernetes, positioning it as a practical upgrade for operators running OpenStack clouds in environments where performance, resilience and operational efficiency matter more than marketing gloss. The release is officially listed by Mirantis as a supported 26.1 version dated March 10, 2026, and the company says it is available now to customers and partners.
What stands out in this release is that Mirantis is trying to reduce operational friction at several layers at once. The headline feature is an AI assistant for documentation and operational guidance, aimed at helping cloud operators ask task-focused questions instead of manually digging through documentation trees. In practice, that matters because OpenStack and Kubernetes environments are powerful, but they are rarely simple. When a platform vendor adds a documentation-grounded assistant, the real value is not novelty, it is faster troubleshooting, less time wasted in procedural lookup, and potentially more consistent operations across teams. Mirantis is explicitly framing this assistant as a way to deliver answers from technical documentation and connected knowledge sources.
The second notable move is around energy and cost awareness. MOSK 26.1 adds the ability to track energy consumption and correlate workloads with power cost, which feels especially timely for GPU-heavy infrastructure and so-called AI factories. That is a meaningful addition because AI infrastructure economics are increasingly shaped not just by hardware acquisition, but by sustained electricity demand, thermal load and utilization efficiency. In other words, this is the kind of feature that turns infrastructure operations into a more financially visible discipline, which cloud providers and enterprise platform teams have been drifting toward anyway.
On networking, MOSK 26.1 appears to be a serious upgrade rather than a token checklist release. Mirantis highlights expanded OVN support, including VPNaaS for secure connectivity between OpenStack clouds and on-premises environments, as well as between projects across MOSK clusters. It also adds quality-of-service controls for north-south traffic and SR-IOV support for lower-latency, higher-performance workloads by allowing virtual machines more direct access to network hardware. For operators serving AI inference, NFV-style deployments, or premium tenants with strict performance expectations, those are not cosmetic improvements. They go directly to determinism, segmentation and throughput.
The rest of the release rounds out the story in a way that suggests Mirantis is chasing production credibility. Granular restrictions for access to Instance HA through OpenStack Masakari let operators align failover behavior with business priority and infrastructure capacity instead of treating every workload the same. Cryptographically signed SBOMs in CycloneDX format strengthen software supply-chain visibility, which matters even more in regulated sectors. Backup improvements for management clusters, including external storage support, encryption, scheduled workflows and automatic pre-update backups, are the kind of details that rarely make flashy headlines but do shape whether a platform feels safe to run at scale.
Taken together, MOSK 26.1 looks less like a dramatic reinvention and more like a sharpened operator-focused release. That is probably the right move. OpenStack is still relevant where organizations want cloud-like control without handing everything to hyperscalers, and Kubernetes-native packaging gives Mirantis a way to argue that OpenStack can remain modern without pretending the last decade never happened. The AI assistant will grab attention, sure, but the deeper significance of this release is that Mirantis is trying to make complex infrastructure more governable, more measurable and a bit less punishing to run day after day.
Leave a Reply