Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Kubernetes on Oxide: How customer needs shaped our integrations

oxide.computer

Post reply on HN
Print view View original

71–73 of 73 posts

Re: Kubernetes on Oxide: How customer needs shaped our integrations

#71

Post by maxgashkov »

lkasjdas wrote: post #36
pianoben wrote: post #4

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...

Every single Oxide article has comments about people wanting one at home. A great example of completely misdirected marketing and/or engineering. Oxide should have developed home microcomputers, and they would have sold like cupcakes, with their ASCII art marketing. Instead they do million dollar "mainframes" that no one (except VCs) wants to buy.

While I'm fascinated by Oxide, their style and work culture (if open documents are to be believed), I do think you're misunderstanding the homelab people a lot. Yes, I want the chance to play with an actual Oxide hardware in the same sense I'd want to touch a mainframe from the 80s. In the end though this is an extremely opinionated piece of tech that doesn't really invite or support tinkering. And homelab is about building something that no sane production-grade maker would ever be doing, so selling to this market would be quite an insane business venture.

Re: Kubernetes on Oxide: How customer needs shaped our integrations

#72

Post by bakies »

fragmede wrote: post #66
bakies wrote: post #43

Earlier quoted context omitted.

What's a cloud? K8s is a cloud imo, so is what oxide is providing afaict

Cloud is an API you can hit to get access to hardware. Oxide sells hardware.

Oxide has an API on top that gets you services. The whole pitch is AWS with purchased hardware, no? That's cloud

Re: Kubernetes on Oxide: How customer needs shaped our integrations

#73

Post by moondev »

sudomateo wrote: post #31
bitlad wrote: post #19

I am wondering when would you use kubernetes on oxide vs running kubernetes with kubevirt on baremetal? At first look, it feels like oxide is equivalent to proxmox or some virtualization tool, may be it uses qemu stuff underneath. Just curious. The reason I am asking this is that, we have lot onprem scenarios in our business. We are tightly coupled with k8s, to solve this we started building an internal project that…

Good question. We use our own hypervisor[0] that's not KVM/QEMU. We don't have nested virtualization today so we don't follow the KubeVirt model, though we are discussing what CRDs like OxideInstance would look like for those that want to operate solely in Kubernetes manifests. The core primitive on Oxide is the instance (virtual machine). We could support some container primitive, but that's a larger product directi…

Could there theoretically be a swappable hypervisor for oxide some day? I'm imagining a oxide Linux distro of sorts running on the hosts, and using kvm for vms, but still oxide control plane bits downstream. Then you get nested virt and gpu support, and could maybe even virtualize a traditional oxide host. Like running multi-host vcenter clusters inside a single esxi, amazingly powerful lab scenarios, teardown is even fun
Post reply on HN