3 ms·
Or move to minikube and friends. If it's a dev environment you can usually get away with such things.
by blazespin 7y ago
Or move to minikube and friends. If it's a dev environment you can usually get away with such things.
- atombender 7y agoKubernetes consumes a lot of CPU even when idle, due to the polling design, which makes Minikube is a really poor fit for developer machines. It's well known [1] to sit there eating 20-30% CPU, draining your battery and frustrating your life while doing absolutely nothing. This applies to all the Kubernetes distributions, including Kind and Docker Desktop. Not sure if the same applies to K3s, though. [1] https://github.com/kubernetes/minikube/issues/3207 https://github.com/kubernetes/minikube/issues/3207, https://github.com/docker/for-mac/issues/3065 https://github.com/docker/for-mac/issues/3065, https://github.com/docker/for-mac/issues/3539 https://github.com/docker/for-mac/issues/3539, etc; there must be dozens and dozens of these
- rcarmo 7y agoIt does. My k3s setups (like https://github.com/rcarmo/azure-k3s-cluster https://github.com/rcarmo/azure-k3s-cluster) take up nearly 100% of the puny master node I allocate to them, and kill my Raspberry Pi SD cards as well. Swarm, in comparison, is much friendlier (and you can use it for dev/test across multiple machines just fine)