6 ms·
This is extremely welcome. Kube needs to glom on to all available architectures to fulfill its destiny, to some extent, and the memory/cpu usage of kubeapi et a
by erulabs 8y ago
This is extremely welcome. Kube needs to glom on to all available architectures to fulfill its destiny, to some extent, and the memory/cpu usage of kubeapi et al. can be prohibitive for small setups. Having to revert to ansible/systemd in "some cases" really weakens the story of a universal datacenter O/S.
My hope is for more competition for development k8s (or k3s!) - minikube and docker-for-desktop is plagued with high CPU usage problems, and OSX-wielding developers are still doubtful. It will require a lot of work and elbow grease to convince them. I've built a hosted platform that tries to address this, but it's a complex education problem, which I am not well suited to solve :(
- geerlingguy 8y agoAgreed. Kubernetes (installed via kubeadm) on 1 GB of RAM is a shaky proposition at best; I've been managing a cluster on Raspberry Pis and the master often hits swap managing three Nodes with a dozen or so Pods.
- vhost- 8y agoK8s doesn’t support swap, you have to disable swap to even run kubelet.
- phire 8y agoThere is an override flag. It works, but it kind of invalidates all assumptions k8s makes about free memory on a node
- moondev 8y agoWhat workloads are you running? With only 1gb, have you looked into setting resource limits for your pods?
- xur17 8y agoI really want to do this as well - we've just started looking at minikube for our group, and I'd love to use k3s instead, but does anyone know if it works on OSX? I was able to get a cluster running on my laptop in under a minute, which is pretty amazing.
- farisjarrah 8y agoHave you seen or used Microk8s ? Seems like it might be what you are looking for. Can be installed and removed via snap package too