Kubernetes on Oxide: How Customer Needs Shaped Our Integrations
In late 2024, Oxide had no supported Kubernetes integrations, but customers were eager to run Kubernetes on Oxide. This post traces how customer workflows guided the development of three provisioning tools—Rancher node driver, Omni infrastructure provider, and Cluster API provider—plus a cloud controller manager and a CSI driver. Each integration revealed new gaps, from networking to storage, shaping both the software and Oxide's platform roadmap.
The workaround right now is to pad the user-data with comments to increase its size enough that it uses an ISO 9660 superblock.
- stevehipwell
I'm interested to see how the `oxide-cloud-controller-manager` is being built for "modern" Kubernetes and if it leads to any signify difference compared to CCMs that originated in-tree. Given the way Oxide engineer their solutions this could be really interesting.
FYI I've got `karpenter-provider-oxide` on my bingo card...
- pianoben
I have seldom wanted anything as much as I want an Oxide rack at home. Maybe in 40 years we'll start to see the first ones show up in surplus auctions...
- overflowy
I would absolutely kill for them to open source their documentation system.
- lars_francke
Disclaimer: I'm totally biased here.
I talked with a colleague from Oxide in 2024 about your Kubernetes story and he said back then "not yet but soon-ish". Seems like soon-ish is now :)
We said we'd talk again when that happens but he's since left Oxide. If you (or well...your customers) are interested in a Kubernetes native data platform 100% open source we'd be very happy to talk about how that could work easily. As it's "just" Kubernetes it should be trivial but we'd be happy to test and add you to our list: https://docs.stackable.tech/home/stable/kubernetes/#supporte...
The offer stands. If you're interested, my mail is in my HN profile. https://stackable.tech
- moondev
Love to see the CAPOx provider and buy in to Cluster API