Live data from Hacker News

Comparing K3s with vanilla Kubernetes

hoelzel.it

81–90 of 90 posts

Re: Comparing K3s with vanilla Kubernetes

#81
post #37

Earlier quoted context omitted.

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

Been using k3s(kube-vip + MetalLB) and Longhorn for both my personal projects and work projects for a while without any issues. It's a pleasure to use instead of the alternatives.

Interesting combo, care to share more about such a setup?

Re: Comparing K3s with vanilla Kubernetes

#82
post #52

Earlier quoted context omitted.

Ok, I've stuffed "default" in the title above. If someone wants to suggest a better (i.e. more accurate and neutral) title, we can change it again.

I see the term vanilla being used.

Ok let's have some vanilla!

Re: Comparing K3s with vanilla Kubernetes

#83

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…

Don’t throw the baby out with the bathwater.

Re: Comparing K3s with vanilla Kubernetes

#84
post #70

I would lean towards k0s over k3s. The article has one piece of information wrong. K8s no more comes with docker. It is containerd I think.

the only way i would ever trust a mirantis product again is if they dissolve their board completely.

The whole "kubernetes-lens" debacle still burns deep.

Re: Comparing K3s with vanilla Kubernetes

#85

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…

there is a good talk from kelsey hightower on when it makes sense to ue k8s and the number was like 20 servers. i think with what you are describing i would not even think about using k8s.

Re: Comparing K3s with vanilla Kubernetes

#86
IMO K3s (and distros like it) are the future of self managed Kubernetes. The same way Linux distributions brought simplification and sane, opinionated defaults to Linux in an era where compiling your own kernel and throwing user space together, K3s does the same for vanilla Kubernetes. It’s a joy to deploy and manage over vanilla.

Re: Comparing K3s with vanilla Kubernetes

#87

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…

Sounds like Digital Ocean was the problem, not Kubernetes. Been running managed Kubernetes in GCP for years without any issues. They are bugging me to update for some time now, but I don't think they would force an update on me.

Something is always the problem. With a VPS, you don’t usually have to worry about DO being a problem. You pay your bills, your server stays up. Maybe if you don’t update you might get hacked, but killed by provider update is not a failure mode of VPSs. I use k3s on bare metal. I’ve tried to run k8s so many times before and they all failed at some point in ways that didn’t inspire confidence. Mostly etcd became a mess, so this time I’m running k3s with a Postgres datastore that I can actually look at, reason about, backup and independently make HA, with a plus of not having to run arcane commands to manage the cluster that runs my cluster.

I once tried nomad because it claimed to be simpler. I stopped when I realized I’d also have to use multiple clusters to run a cluster (nomad+consul).

I use k3s because I build apps for multiple clients and I like the flexibility that it gives me in running servers like cattle.

My point is that these orchestrators need to start decreasing the enormous amount of risk they add to any project.

Re: Comparing K3s with vanilla Kubernetes

#88
post #57

Earlier quoted context omitted.

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

Can you share more details please? How did you find out it was DO, did you open a support ticket?

well, I'm the only one with access to the cluster and I didn't do it, with Lens IDE I barely check the Nodes tab, I checked the Nodes because I noticed no app pods were scheduling in such node and I found it cordoned.

Re: Comparing K3s with vanilla Kubernetes

#89
post #70

I would lean towards k0s over k3s. The article has one piece of information wrong. K8s no more comes with docker. It is containerd I think.

the only way i would ever trust a mirantis product again is if they dissolve their board completely. The whole "kubernetes-lens" debacle still burns deep.

Sorry I am totally unaware of that. Any pointer to this lense controversy?

Re: Comparing K3s with vanilla Kubernetes

#90
post #89

Earlier quoted context omitted.

the only way i would ever trust a mirantis product again is if they dissolve their board completely. The whole "kubernetes-lens" debacle still burns deep.

Sorry I am totally unaware of that. Any pointer to this lense controversy?

When kubernetes-lens came out it was the greatest software to see what is going on in a clusters.

I have suggested it to basically everyone working with k8s saying its a must have tool and also made many teams install it.

It was a great time for half a year and a lot of the community contributed to it, only to have them turn around and force accounts on all users: https://github.com/lensapp/lens/issues/5444

this turned into an application that now comes with a signed hidden binary, could not be build through the open source repository any more and much ohter things related to this.

All in all Mirantis is not to be trusted, not to mention the fact that the tool wants to share your kube-config amongs your team which is a clear antipattern and a high security risk.

Post reply on HN