←back to thread

Uncloud - Tool for deploying containerised apps across servers without k8s

(uncloud.run)
176 points rgun | 1 comments | 04 Dec 25 06:02 UTC | HN request time: 0.213s | source
Show context
JohnMakin ◴[04 Dec 25 08:21 UTC] No.46145088[source]▶
Having spent most of my career in kubernetes (usually managed by cloud), I always wonder when I see things like this, what is the use case or benefit of not having a control plane?

To me, the control plane is the primary feature of kubernetes and one I would not want to go without.

I know this describes operational overhead as a reason, but how it relates to the control plane is not clear to me. even managing a few hundred nodes and maybe 10,000 containers, relatively small - I update once a year and the managed cluster updates machine images and versions automatically. Are people trying to self host kubernetes for production cases, and that’s where this pain comes from?

Sorry if it is a rude question.

replies(5): >>46145152 #>>46145315 #>>46145389 #>>46145675 #>>46146251 #
esseph ◴[04 Dec 25 09:43 UTC] No.46145675[source]▶
Try it on bare metal where you're managing the distributed storage and the hardware and the network and the upgrades too :)
replies(2): >>46146012 #>>46146025 #
1. JohnMakin ◴[04 Dec 25 10:34 UTC] No.46146012[source]▶
Why would you want to do that though?

On cloud, in my experience, you are mostly paying for compute with managed kubernetes instances. The overhead and price is almost never kubernetes itself, but the compute and storage you are provisioning, which, thanks to the control plane, you have complete control over. what am i missing?

I wouldn’t dare try to with a small shop try to self host a production kubernetes solution unless i was under duress. But I just dont see what the control plane has to do with it. It’s the feature that makes kubernetes worth it.