Hacker News Reader

Comment by m1ghtym0 | Hacker News Reader

How does it compare against minikube? Seems to be based on Snaps vs minikube's VM-based approach. Any other major pros/cons?

View on HN

From my experience of using microk8s for mostly offline development and trying minikube once:

Microk8s pros:

- bind-mount support => it is possible to mount a project including its node_modules and work on it from the host while it hot-reloads in the pod.

- The addons for dns, registry, istio, and metallb just work.

- Feels more snappy than minikube.

Microk8s cons:

- Distributed exclusively via snap => can't be easily installed on nix/nixos.

Thanks!

microk8s also makes it super easy to have a multi-node cluster, even with HA.

I used Minikube constantly for development. The best way to run it is directly on Linux, in which case it does not require a VM and is very stable. VMs on the other hand seem to cause a lot of problems--it's not especially stable on Mac OS and does not seem to survive reboots very well. (YMMV.)

I thought minikibe would not cluster multiple machine ?

Yes, it seems not possibile. You can EMULATE a multi mode cluster but inside a big host machine.

Minikube is very effective on my huble opinion to STUDY K8s becauese it is always strong aligned with K8s releases.

I do not think minikube is a good choice for production but hey, I could be wrong... someone want to share any experience?

Yes, definitely not production. Using them (MicroK8s, Minikube, K3s) for local testing mostly.

Reply on news.ycombinator.com