Live data from Hacker News

Comparing K3s with vanilla Kubernetes

hoelzel.it

21–30 of 90 posts

Re: Comparing K3s with vanilla Kubernetes

#21
post #11
post #6

Earlier quoted context omitted.

That's the joke, though? It's k8s, but "smaller".

What are the three letters? It only makes sense for being confusing, which is the base state of Kubernetes. "Our name is literally a complex joke about complexity" doesn't inspire confidence in a project that supposedly simplifies complexity.

Kubernetes is often shortened to k8s, which is often pronounced "kates," which is further shortened to k3s.

Re: Comparing K3s with vanilla Kubernetes

#22
In addition to K3s, I've used managed K8s, custom-rolled K8s, as well as various other K8s distributions. K3s has - by far - provided the least friction for most of my use cases, and is what I incorporate in any initial cloud design.

Of course, other stakeholders and constraints may eventually mean that we adopt something else before it gets implemented, but K3s is what I start with for many of the same reasons outlined in this article.

Re: Comparing K3s with vanilla Kubernetes

#23
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

while true, writing "vanialla kubernetes" did not have the right feel for me.

What would have been a better title for you?

Re: Comparing K3s with vanilla Kubernetes

#24
post #11

Earlier quoted context omitted.

What are the three letters? It only makes sense for being confusing, which is the base state of Kubernetes. "Our name is literally a complex joke about complexity" doesn't inspire confidence in a project that supposedly simplifies complexity.

Kubernetes is often shortened to k8s, which is often pronounced "kates," which is further shortened to k3s.

Isn't it actually keigths which means it should be k5s?

Re: Comparing K3s with vanilla Kubernetes

#25

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

DigitalOcean also cordons Nodes for no reason at random times. Currently moving to EKS exactly for this reason

Re: Comparing K3s with vanilla Kubernetes

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

you can easily still use external etcd if you really need to.

But in general k3s can be HA without issue and scaled just as well as vanilla k8s. The main advantage of it is that everything comes neatly packed into a single binary whereas the alternative would mean to have a multitude of services running for cluster provisioning.

Kubernetes in the end is basically an API server with multiple componets and k3s puts a nice bow around all of them.

Re: Comparing K3s with vanilla Kubernetes

#29

hmmmmm no mention of pvcs eh

Longhorn ( https://longhorn.io/ ) has been stable for a long time now and is also a could native foundation project =)

You can start with a single storage node without replication and easily go from there to triple replicated storage

Re: Comparing K3s with vanilla Kubernetes

#30
post #12

Been using k3s in production for nearly four years now and would recommend it to anyone. Super lightweight and easy to deploy. Opinionated about stuff I don't care about while allowing for customization of network stack, backing database, and ingress controller if you want to do it yourselves. Their embedded etcd is way, way easier to set up than a custom etcd distribution.

I have built clusters for clients with k3s too and it has always been a charm. More recently i was able to bring up a Dualstack cluster for a VOIP company that now can basically scale endlessly with gitops on top.

The fact that you can integrate existing Sysadmin Teams because they will understand that a program that runs a service with a binary and a config is all it takes, is worth its weight in gold.

They know their Loadbalancers and haproxies as well as how to provision true raid systems that are not software based which almost makes disk failure go away and maintenance really sheduleable.

Post reply on HN