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

61–70 of 70 posts

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

#61

Post by urams »

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.

This is the perfect example of a delusional HN comment. None of it makes any sense, most notably the idea that VCs are buying any of this server hardware.

It's so bad I can only guess that it's purposefully so. "sell like cupcakes"????

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

#62

Post by 27183 »

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.

Favorited. Assuming this comment must be satire.

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

#64

Post by sgarland »

asa400 wrote: post #54
lkasjdas wrote: post #36

Earlier quoted context omitted.

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.

Homelab tinkerers are essentially a non-market. They barely want to pay for the cheapest commodity hardware. Tens of individuals would buy Oxide racks or theoretical microcomputers with their own money.

Unfortunately yes. I would realistically pay about $10K for a MicroOxide rack, because that’s what I can justify spending on what is essentially a hobby. I know that’s never, ever going to happen.

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

#65

Post by ninkendo »

I’ve tried so hard to figure out what the hell oxide even is, but the website is utterly impenetrable. I guess it’s an “integrated platform” and does “AI” and it’s “purpose built for frontier workloads”, but… I have absolutely no idea what it is, still.

I guess it’s a bunch of computers. It says “AMD” in a bunch of places so, I guess they’re x86. Where are the GPU’s? If it’s for “frontier workloads”, wouldn’t those be sorta important? Is it its own OS? No idea. I see people adjacent to Oxide mention IllumOS sometimes[0], so does that mean it’s a solaris-like OS? Why would I want to run k8s (presumably with linux containers) on a not-linux OS? Or does it virtualize linux instances?

Do actual CTO’s go for this type of marketing, with zero details and nothing but pure fluff about “solutions”?

[0] This of course is from HN comments, I see no mention of any operating system whatsoever on the website, so if it is IllumOS, it’s not like you can easily find that info anywhere.

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

#66

Post by fragmede »

bakies wrote: post #43
bitlad wrote: post #32

Earlier quoted context omitted.

Coreweave is a cloud provider right? I dont think it is apple to apple comparison.

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.

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

#68

Post by fragmede »

mixmastamyk wrote: post #30
bcantrill wrote: post #5

Earlier quoted context omitted.

Are you referring to our RFD system?[0][1] Because if so, good news![2] [0] https://rfd.shared.oxide.computer/rfd/0001 [1] https://oxide-and-friends.transistor.fm/episodes/rfds-the-ba... [2] https://github.com/oxidecomputer/rfd-site

Why would a “doc system” use React?

Why shouldn't a doc system use React? One word answers consisting of the word bloat are not going to be accepted, please use your words and be specific. The router sucks, the language is ass, give details!

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

#69

Post by mixmastamyk »

fragmede wrote: post #68
mixmastamyk wrote: post #30

Earlier quoted context omitted.

Why would a “doc system” use React?

Why shouldn't a doc system use React? One word answers consisting of the word bloat are not going to be accepted, please use your words and be specific. The router sucks, the language is ass, give details!

It’s best for SPAs. A pile of docs and comments does not require nor gain much from it. i.e. a poor tradeoff, at first glance anyway.

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

#70

Post by nunez »

Great post.

ClusterAPI never got the love that it should. I spent a good amount of time on it at VMware, as Tanzu heavily leverages it for cluster deployment (mostly CAP-A and CAP-V). It's basically kubeadm + the spirit of Terraform, Kubernetes controller edition. There's lots of great enterprise-ready options for centralized k8s cluster fleet management these days, but it works really well for folks that are all-in on GitOps and such.

Post reply on HN