Just to be clear, though this did seem to get cleared up below, the level of abstraction you're working with on an Oxide rack is VMs, not k8s. If you wanted to run your own k8s on top, you could.
> because they’re not able to set it up themselves sounds insane to me
It is not about ability. It's about quality, and what you want to spend time on vs what you want to spend money on. (and of course time is money...)
There's a lot that goes into building and maintaining a private cloud. Some would prefer to build it themselves, some would prefer to focus on their core business and buy something that works well out of the box.
> What’s the plan when it breaks? Send the server back?
Building a robust product is very important to us, but so is supporting it. If something breaks, you contact support, and it gets sorted.
An advantage here is because we have created almost everything ourselves, under the same roof, we have fantastic insight into how the system works. No pointing the blame at some other vendor's firmware!
If that illusion breaks and you need to get into the weeds in the same way you do with self-hosted k8s, then the value proposition of their product goes poof. I'm just speculating, of course.
Yeah that was my reference point - cluster at home. Breaks often & hard and usually end up wiping it. Good for home use but I’d not want to rely on it for prod
> buying an out of the box k8s because they’re not able to set it up themselves