Kubernetes For AI: CIQ Packages The Moving Parts Into One Binary 

Kubernetes is complicated; get over it. 

That’s kind of the mantra that has come from many vendors in the K8S space, the industry bodies and organizations that support (and promise to mitigate) those complexity challenges, and many in the community itself.

As all good cloud-native developers know, Kubernetes complexity stems from the many interconnected components needed to run production workloads, including networking, storage, security, monitoring and scheduling. Each brings its own configuration, dependencies and upgrade cycles. If we also accommodate complexities related to hybrid cloud, multiple Linux distributions, GPU infrastructure and compliance demands, the operational burden quickly compounds.

Open Source K8S For The AI Era

Known as the company behind Rocky Linux, CIQ has this month introduced CIQ Stratum Kubernetes Engine (SKE) and positioned the technology as “open source Kubernetes for the AI era” today.

Presumably aiming to give the likes of Red Hat, SUSE, Mirantis, Nvidia and the three major hyperscalers a run for their money in the OSS K8S AI zone, the company reminds us that Kubernetes runs in production at 82% of organizations that use containers, and the Cloud Native Computing Foundation (CNCF) calls it the de facto operating system for AI. 

But, says CIQ, running it still means assembling about ten upstream projects that each release on their own schedule. SKE ships them as one signed file that installs, joins, and upgrades the cluster.

Built from an unmodified upstream source by the team behind Rocky Linux, Fuzzball, Warewulf, and Apptainer, CIQ Stratum Kubernetes Engine (SKE) lets system administrators, developers and platform engineers run Kubernetes next to their existing Linux, HPC, and GPU infrastructure.

Kubernetes In A Simple Package

Speaking exclusively to Cloud Native Now, Peter Nelson, chief technology officer at CIQ, says that Stratum makes the power of Kubernetes accessible in a simple package. 

“Traditional Kubernetes is a multi-step process to deploy and configure. Ours is a single binary, with a visual interface alongside the command line, so it’s simple to get started with whether you’re a developer or an agent,” said Nelson. “That means a developer can stand up Kubernetes right there on the desktop and perfect the solution in the exact same environment used in production. They can task the agent with setting it up and be running in minutes, and that agent can only do what the developers allowed it to do. Because the same binary runs Stratum at scale in the cloud, what the developer builds and tests locally runs exactly the same way once they push it to production. It’s never been this easy, and never this enjoyable to work with.”

In general terms, Nelson and team also tell us that the hard part of Kubernetes starts after the first install, when projects drift apart. CIQ Stratum Kubernetes Engine (SKE) pins and tests every component as a set. Rolling upgrades check node health at each step and roll back a node that fails. Further, etcd snapshots (regular backups of Kubernetes cluster configuration and state data) run every 12 hours by default, and certificates renew before they expire. Every release is signed and ships a software bill of materials. 

What a team learns on its first SKE cluster carries to the tenth.

37 Tools: Read, Write, & Destructive 

A built-in MCP server lets AI agents work with the cluster under rules the operator sets. Its 37 tools come in read, write, and destructive tiers, and tools above the enabled tier are never registered. Kubernetes access controls still bound every call, and secrets stay off limits. An AGENTS.md file guides agent-driven installs, and the documentation is published in llms.txt format. Operators get a built-in web dashboard with pods, logs, and shell access.

In a 2026 industry survey of 785 Kubernetes decision makers, 62% said complexity was slowing business initiatives, and 65% ran air-gapped clusters. Teams want speed without vendor lock-in or the cost of integrating every piece themselves.

“Anyone who has stood up a cluster by hand knows the install sets the tone for everything after it, so we built CIQ Stratum Kubernetes Engine (SKE) around getting that step right. Build something on your laptop that works, and the same binary runs it on a cloud VM. What is easy for you to set up is just as easy for your agents to deploy, prototype, and test with,” said CIQ’s Nelson.

CIQ Stratum Kubernetes Engine (SKE) is free and open source and runs a single cluster with an included web UI. CIQ Stratum Pro, the commercial version, manages every SKE cluster, from GPU clusters to the general fleet, through the same web interface under one sign-on. Stratum Pro adds an app catalog, an optional CIS hardening profile with a per-control check, and support from CIQ. Its fleet agent connects outbound only, so clusters need no inbound ports. Cluster API provisioning follows in a later release.

SKE Compatibility & Availability

CIQ Stratum Kubernetes Engine (SKE) runs on any Enterprise Linux 9 or later distribution, so teams keep the operating system they already trust and avoid a vendor’s own node OS. That includes Rocky Linux, RLC Pro AI, and RLC Pro Hardened, on amd64 and arm64. It works alongside Warewulf Pro for node provisioning, Fuzzball for HPC and AI workflows, and Ascender Pro for automation, and each product also runs on its own.

CIQ Stratum Kubernetes Engine (SKE) is available now in technical preview, with general availability expected November 5. SKE is free and open source under the Apache 2.0 license. 

CIQ Stratum Pro is a commercial subscription, with pricing announced at general availability. Both versions download from CIQ Depot and the CIQ Portal; one binary per architecture and documentation is public at docs.ciq.com.