2 ms·
Is a single node k3s overkill? I don't think so. Once you outgrow it, you can port your deployments to a real k8s cluster.
by linuxftw 4y ago
Is a single node k3s overkill? I don't think so. Once you outgrow it, you can port your deployments to a real k8s cluster.
- bongobingo1 4y agoFrom what I have ever seen, even k3s has a reasonably heavy memory requirement for cheap vps instances, vs docker-compose. I think they target different markets. e: I went to re-check, and running the default get.k3s.com install instructions had k3s using 30-35% of 1GB of memory, without anything running. Thats pretty meaningful on low resource machines like a RPI, NAS, $5/vps etc. Also FWIW, Hashicorp Nomad uses ~3.5% on the same machine (but provides less than k3s, more than compose).
- linuxftw 4y agoI mean, if you're in the realm of 'no-downtime upgrades' because it will impact your application, maybe spending an extra $5/mo makes sense rather than relying on bespoke tooling. There's also k0s, which aims to be even lighter than k3s.