k3s

“today it's fairly simple to setup a single node deployment with minikube or k3s”

“It also breaks a lot and does add a whole bunch of complexity”

“Simple k3s cluster and the shallow end of kubernetes actually saves you a ton of time and effort”

“The overhead of a simple k3s setup to bind a couple nodes into a cluster is similar to docker compose”

“ask your frontier LLM agent of choice to configure kubernetes (on something like k3s) with mandatory userns mapping so nothing runs as root on the host”

“a small k3s cluster is ideal to make use of all the resources you can throw at it”

“It has a low resource footprint and is well suited for running on VPS boxes.”

“dodgy curl piped to bash scripts that users install without question”

“Instead I have k3s where I just need to remember to update the internal certificate once a year.”

“I think single node kubernetes is very underrated, both for running a single project or for multiple.”

“it feels like a real cluster but it's all on a single piece of hardware which makes snapshots etc super simple”

“All those abstractions and cluster features do not come for free.”

“K3S takes about 5 minutes to setup the first time and you instantly have an entire universe of standardized operational tooling.”

“it still takes someone dedicated to babying it”

“using something like K3s is quite straightforward and lightweight on resources”

“maintaining a lot of complexity for limited benefits”

“A single server with k3s is basically docker compose + the possibility to use helm”

“The problems you describe having below are problems with peripheral components, not k3s itself.”

“lots of areas where documentation is just plain wrong”

“You can bootstrap k3s with "curl -sfL https://get.k3s.io | sh -". If you need to do that over ssh it works just fine.”

“There is lot of operation complexity in general and most of us can do without.”

“We have been running into lot of issues at production with k3s.”

“I do run a k3s cluster for home stuff... But I really wish I could get what it provides in a much simpler solution.”

“Kubernetes, in the form of k3s, was a critical success factor for us with the onprem deployment of our SaaS product.”

“a single, unified, standardized, extensible control plane that lots of software already supports”

“run reproducible runtimes like k3s or devcontainers so environments stay consistent”

“There's something nice about using git to add a helm repo, a helm release with a few values, then 'git push'.”

“Not a fan of their curl -sfL https://get.k3s.io | sh - installation method”

“k3s is pretty lightweight, easy to install, and there's a lot of great tooling for k8s”

“just use k3s or k0s and you will still benefit from the absolutely massive ecosystem”

“I'd take a simple 3-node k3s cluster over hacked-togther compose files and glue scripts any day.”

“k3s is a good non overkill alternative while benefiting from everything k8s offers.”

“You drop a single binary onto the node, run it, and you have a fully functional one-node k8s cluster.”

“k3s makes it easy to deploy, not to debug any problems with it.”

“I do remember having to touch the K3s YAML directly, and maybe having issues also persisting it”

“resetting k3s in NixOS is not that straightforward and requires manual input”

“It's slightly (but not hugely) easier to work with then the prior version that I had running under IIS.”

“Alternatively use K3s and Flux to end up with a solution that checks all of those boxes”

“Absolutely recommend k3s. Start with a single node and keep on scaling as customer base increases.”

“I use k3s for my home and for dev envs I think it's completely fine especially when it comes to deployment documentation.”