4 ms·
k3s is so 2019. Kind is where it's at. /s Personally, k3s is good for bare-metal since it's slightly lighter-weight than a kubeadm-provisioned cluster. However
by nunez 5y ago
k3s is so 2019. Kind is where it's at. /s
Personally, k3s is good for bare-metal since it's slightly lighter-weight than a kubeadm-provisioned cluster. However, I found it too heavy-weight for running k8s on a laptop. I believe it uses etcd, which is pretty noisey.
Kind is a lot lighter, I've found. And it runs in Docker, which is great. I haven't tried using it for more complex stuff like service meshes and storage; I'd expect issues there since it's pretty stripped down. For local testing, however, it's solid.
I've heard k0s is similar.
- cococonut 5y agoKind is also used as the reference implementation for kubernetes, so you know it’s compliant and won’t have weird mismatch bugs.
- raesene9 5y agoFunny you say that as one of k3s main difference to general Kubernetes is that it supports the use of sqlite instead of etcd, whereas kind is straight kubeadm clusters in Docker containers, so uses etcd... I see the two projects as covering largely different ground. kind is brilliant for test clusters where you don't need long term persistence, but k3s is better for long-term low resource clusters.