Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

K3s – Lightweight Kubernetes

k3s.io

Post reply on HN
Print view View original

121–130 of 196 posts

Re: K3s – Lightweight Kubernetes

#121

Post by sleepybrett »

umvi wrote: post #116
sleepybrett wrote: post #104

Earlier quoted context omitted.

I find it very acceptable on my local servers that run my mail, web, mastodon, etc servers. I prefer the configuration in kubenetes templates instead of spread all over my filesystem in /etc (config in one place and fucking unit files in another), /var/lib, /opt, etc.

Right, you've acquired the taste. But why should people who haven't acquired the taste do this? To me seems like a mountain of unneeded complexity compared to just running a local webserver directly in a docker container with "docker run --restart always ".

Turns out to run the stuff I run I need more than 1 machine :).. luckily a couple of years back when my job was dissolving a dept and had a stack of uneeded NUCs headed for recycling (pretty nice ones, i've added a little ram but that's it) I tossed them in a box and took them home instead. I've also added a couple of PI/Arm nodes just for kicks.

Re: K3s – Lightweight Kubernetes

#122

Post by selljamhere »

I had a great k3s experience with a silly, over engineered weekend project to automate my fog machine with motion sensors.

I connected motion sensors to battery & wifi enabled RPis, built a remote circuit to control the fog machine, and ran a k3s cluster with NATS to bring it all together. 10/10 would do again.

https://blog.apartment304.com/fog-machine-madness/

Re: K3s – Lightweight Kubernetes

#123

Post by MrOwen »

ozarker wrote: post #48
mpsprd wrote: post #6

Can this tool help to simplify self hosting implems? K3s was recommended to me to replace my personal pile of systemd units starting docker compose configs and manual reverse proxy configs. Im am completely oblivious to how k8s works.

I use it for self hosting. It really simplified my reverse proxy config like you said. I use the internal networking between services quite a bit. I have it auto-provisioning volumes on my NAS and using them via NFS. I love it to death and would say it has simplified my setup overall. But the upfront cost of learning k8s is indeed high.

Seconding this as well. Similar setup (though I opted for longhorn) and journey. I'm very grateful for learning k8s but man, it was definitely rough for a long while until I really understood all the pieces and cemented my understanding. I can very much appreciate that's a tall order for many people and not wanting to embark on that journey unless there's a good reason.

Re: K3s – Lightweight Kubernetes

#124

Post by imiric »

intangible wrote: post #78

I've been using a 3 nuc (actually Ryzen devices) k3s on SuSE MicroOS https://microos.opensuse.org/ for my homelab for a while, and I really like it. They made some really nice decisions on which parts of k8s to trim down and which Networking / LB / Ingress to use. The option to use sqlite in place of etcd on an even lighter single node setup makes it super interesting for even lighter weight homelab container environ…

Thanks for your perspective.

How has your experience been with Longhorn? Performance, flexibility, issues, maintenance...? I'm interested in moving away from a traditional single-node NAS to a cluster of storage servers. Ceph/Rook seem daunting, and I'd prefer something easy to setup and maintain, that's performant, reliable and scales well. Discovering issues once you're fully invested in a storage solution is a nightmare I'd like to avoid. :)

Re: K3s – Lightweight Kubernetes

#125

Post by outime »

umvi wrote: post #103

Kubernetes seems like an "acquired taste". Either you use it a lot (likely at work) and are therefore comfortable using it outside of work as your one-size-fits-all solution to everything, or else you don't use it a lot and see it as a complexity behemoth that hides all of your system behind esoteric CLIs and config files that just make everything a nightmare to manage.

I'm tired of seeing comments with an apparent layer of objectivity which very quickly goes away as you reason about it for a second. You could've just said "I don't like K8s, it's too complex for my taste" but then your comment would be gray for being short and concise, so you decide to say this.

Opinions are fine and you may as well hate K8s or any tech being discussed. I just hope to see less of "people who like this just because they don't know any better vs the smart ones like me who know The Truth™" comments.

Re: K3s – Lightweight Kubernetes

#126

Post by hobofan »

umvi wrote: post #102
OhSoHumble wrote: post #77

Earlier quoted context omitted.

I've commented on this before in a different k8s thread (one about a k8s outage) but something that bears repeating is that the entire job market is Kubernetes. My personal experience is that it is very, very hard to find a job right now if your professional experience is primarily non-k8s orchestration systems. Most job positions out there require deep Kubernetes knowledge as well as hands-on experience with differe…

A lot of smaller SaaS companies avoid k8s like the plague and only start using it once they scale to a certain size. K8s might be ubiquitous past a certain scale, but there are many jobs operating below the threshold for which the complexity of your system with k8s outweighs the complexity of your system without k8s.

If you find yourself on the Google cloud for some reason, GKE Autopilot is such a great hands-off solution that most alternative solutions will probably be more complex.

I only recently had to use AWS EKS, and am pretty sure that many people dislike k8s because that's the main incarnation of it they experience (how is there no pre-installed ingress, and even the setup for their own load balancer is a 10+ step manual process?).

Re: K3s – Lightweight Kubernetes

#128

Post by nullify88 »

mfer wrote: post #36
diggan wrote: post #17

"Lightweight Kubernetes" and then a graph involving 2 different nodes with 10+ services running on them. Nomad seems to be a truly "lightweight Kubernetes" and for the small amount of time I've been using it, it seems to do it's job really well and it's easy to understand all the moving pieces without spending countless of hours reading docs and source code. Although, it's hard to recommend Nomad for future uses as i…

You can run k3s with a single node. In that case it uses sqlite instead of etcd which is great for a smaller resource footprint. If you're comparing k8s distros, you'll be hard pressed to find a setup that uses fewer system resources.

Is it actually smaller though? For those non etcd data stores, Kine is often the component doing an etcd to database translation. Im my experience using it generated a load that was greater than a one node etcd instance.

Re: K3s – Lightweight Kubernetes

#130

Post by [deleted] »

sleepybrett wrote: post #112
tarruda wrote: post #44

Earlier quoted context omitted.

> K3S is for orchestration across nodes, and by design you can't run services on the master for security reasons unless you manually change it. That has not been my experience with k3s. Unlike normal distributions, k3s servers do allow workload to run on them unless you manually disable. From https://docs.k3s.io/datastore/ha-embedded : " An HA K3s cluster with embedded etcd is composed of: - Three or more server node…

This is not true of k8s in general, maybe certain on prem 'distributions' enforce this, i'm not sure. Sometimes kubernetes admins/operators who are running their own control planes and etcd will run etcd on non k8s controlled nodes, or they will run it on the same nodes that run their control plane services (scheduler, apiserver, controller manager, etc). Often those nodes will be tainted in such a way that they don'…

[deleted]
Post reply on HN