4 ms·
The article is wrong.... > microk8s – a Snap distribution of Kubernetes. Only for Linux. Not sure why you would use it. Minikube has been far more battle-teste
by ethernet 5y ago
The article is wrong....
> microk8s – a Snap distribution of Kubernetes. Only for Linux. Not sure why you would use it. Minikube has been far more battle-tested and is multi-platform, and doesn't require lock-in to a pseudo-package manager.
microk8s is available on macos, and works well from my limited testing of it
https://microk8s.io/ https://microk8s.io/
- rckrd 5y agoIt requires users to install multi pass. You can run any of these tools in a virtual machine
- rb12345 5y agoI'd say the main argument for using microk8s over minikube is that Canonical supports it, assuming that's a relevant concern. The issue for both microk8s and minikube is how to actually build the containers in the first place. With Docker Desktop or the Docker Engine on Linux, you can use "docker build" to build them. Without that, you need to install a separate tool to do the build (buildah/podman/generating tarballs by hand?) and then push it into a suitable registry or import it into Kubernetes.
- merusso 5y agoThe author doesn't point this out well, but Minikube allows you to pretty easily expose a remote Docker host to be used for `docker build` and other Docker API commands. The command is `minikube docker-env`, which defines env vars that point the `docker` CLI client at Minikube's Docker API.
- afbjorklund 5y agominikube now includes a command called "minikube image build", which builds the images for your Kubernetes cluster - for any container runtime, including docker - but also containerd