k3s
Fewer than 5 people recommend it so far, so there's no written verdict. Here is what commenters said.
3recommend
0warn against
Feb 16, 2026first mention
Oct 23, 2026latest mention
Why people recommend it
“on a small k3s cluster on my desk. You could do the same even with a single node cluster.”
“there are products like k3s that are very simple to use”
Show 1 more
“I use k3s for my home network because it's simple and easy”
runs home networkon “Docker Swarm vs. Kubernetes in 2026”
Caveats and dissent
No one in these comments warned against it.
Often compared with
Who recommends it in their own words
Threads where it came up
- OpenShell – A safe, private runtime for fleets of autonomous AI agents 1 mention
- What I self-host 1 mention
- Vagrant is approaching EOL. No more "Docker for VMs" 1 mention
- Run isolated sandboxes with full lifecycle control: AWS introduces MicroVMs 1 mention
- Ask HN: Looking for a CI/CD project for my local lab 1 mention
- Ask HN: What are you working on? (June 2026) 1 mention
Also written as K3s. Data: k3s.json. Quotes are verbatim; the verdict and theme labels are written by a model from these comments, and every clause links to its sources.
All comments 10
“a proper sandbox (actually 2 security tiers there) setup in a k3s namespace”
“The kubernetes cluster is k3s”
“Vagrant for VM provisioning and K3S for the rest.”
“I managed to get Kubernetes (k3s) running across a cluster of MicroVMs.”
“on a small k3s cluster on my desk. You could do the same even with a single node cluster.”
“moved all of my local inference services to k3s across 3 RTX 4090 PCs and my DGX Spark”
“there are products like k3s that are very simple to use”
“Stack is 15+ Go microservices on k3s.”
“Now all of this is running deployed in k3s.”
“I use k3s for my home network because it's simple and easy”