Live data from Hacker News

Comparing K3s with vanilla Kubernetes

hoelzel.it

1–10 of 90 posts

Re: Comparing K3s with vanilla Kubernetes

#8
It was 01:30. About to go to bed. Next day would fly with my daughter to holidays.

I checked the apps of a bunch of clients. None of them loaded. I was like what...

I checked the server. Everything down.

I'd been running Kubernetes on Digital Ocean. And Digital Ocean forced a Kubernetes update that was incompatitable with mine at night.

Took me 8 hours to fix it. No sleep. Ended up moving it back to a good old VPS. And throw away K8s.

Now to be fair, I had been getting warnings with deployments. But I was used to that, Kubernetes has 10 updates per week. I dont have time to update K8S or my helm files every week.

So yeah it was my fault, but I was used to good old VPS hosting. There is an old php application I've build 5 years ago with Laravel, that never needs anything. I did some updates and patches, but it always just works.

Im used to running node on apache or nginx, even though a bit less stable, still almost never crashes.

Kubernetes there is always something. I guess there are reasons to choose it, but it's not stability.

I ended up taking the plane, and my daughter was super kind and patient. But no more kubernetes for me.

Re: Comparing K3s with vanilla Kubernetes

#9
post #5
post #3

the title doesn't make sense, it reads like "comparing Ubuntu with Linux, How Ubuntu is often the better choice". k3s is a kubernetes distribution

What is the official kubernetes distribution called?

There isn't one — the official docs give instructions for kubeadm, kOps, and kubespray. k3s would be an alternative to those.

Re: Comparing K3s with vanilla Kubernetes

#10
post #7

Is there any advantage of running k3s if you want to keep etcd? I understand that most k3s performance gains come from etcd being replaced by sqlite but if you still want a HA control plane, sqlite won't cut it.

We've been using k3s' embedded etcd for as long as its existed, and it's great. Setting up the etcd cluster is dramatically simplified; let the first node generate a token and feed it to all the other nodes. Tons of other advantages to k3s; the single-binary deploy process, the built-in networking stack (which you can secure with Wireguard out-of-the-box), built-in ingress controller if you want one.
Post reply on HN