Hacker News Reader

Comment by grabcocque | Hacker News Reader

There's minikube. There's been minikube for a long while.

Minikube (and its derivative, MiniShift) have been very helpful for my team in bridging the gap between local development and production for Kubernetes and OpenShift.

Thanks... Would love to know more about your experience.

/me is one of the main contributors of Minishift

As an ordinary developer, I'd love to hear your experience as well.

Note that minikube is built from docker's libmachine that was used in the pre-moby Docker Toolkit.

Yes. And I don't mean to knock minikube, but this is potentially simpler and easier to use.

I don't see how it could be much simpler and/or easier. In my experience, Minikube just works, out-of-the-box.

Not everyone had the same experience.

There a few minor UX flaws that make it frustrating to use, e.g. having to set Docker host, shared filesystem performance is poor, networking in enterprise desktop environment is broken (just to name a few top most issues).

Also, a lot of folks end up running Docker for Mac and minikube VMs, why should they have to run two VMs?

Additionally, minikube is completely different from production-grade deployments (single binary, which means a rewrite of main function for etcd and all control plane components, as well as hard to debug basic performance issues in control plane, there is one large process and you don't know what is wrong, also there is no way to use your favourite network add-on).

Additionally, minikube is based on legacy Docker libmachine, it is not really maintained anymore.

Certain things are not possible. However, we try to match functionality as much as possible with localkube (and soon kubeadm).

Shared folders, especially using 9p and/or cross-platform have been an issue, and I personally also experience this in the fork Minishift, and this likely the performance issue you meant.

But back to an earlier question I posted, have you filed the issues you had in the issue tracker? https://github.com/kubernetes/minikube/issues

Yes, the docker/machine code is an issue. For this, the libmachine is mostly moved inrepo and we are working on abstracting and even replacing this.

Yeah, not to pile on with the comments, but more to help someone else who might not have used minikube, but it's been great for the past year we've been using it. As simple as simple gets.

So in reading this link where information is scarce, this seems like an alternative to minikube (e.g., bundling Kubernetes as part of Docker CE/EE). Is that the right interpretation?

FWIW, we've found minikube a bit wonky. It's resource intensive, so if you want to run more than a couple services, your laptop starts to melt. One of our open source projects is Telepresence which relies heavily on Kubernetes networking, and we definitely see more weird/networking issues with Telepresence/minikube than with regular K8S clusters.

Have you filed an issue about this behaviour?

Note: resource intensive might be because of the hypervisor but generally shouldn't be that bad.

Docker for Mac and Windows will include a single node k8s cluster, so yes, effectively a replacement for minikube. Docker EE will include full support for k8s as an orchestrator as well as Swarm mode.

I like minikube for some things, but I'm hoping this will be better by allowing for multiple K8s nodes to be spun up which is handy for some learning/training scenarios

Is there an easy way to build an image locally and start it in minikube without an external registry or running a local one?

yes. `eval $(minikube docker-env)` will setup the docker cli to use minikube's docker demon.

https://kubernetes.io/docs/getting-started-guides/minikube/#...

We use minikube's support for Docker insecure registries to build and deploy images locally. It works perfectly for us.

i guess the easiest way would be to run a registry in minikube.

another approach would be to run docker inside a k8s-pod (docker-in-docker), that way you can run images without having to push them to a registry but still test it in k8s-environment (at least to some extent).

which is actually just docker-machine. This could be a infiniately simpler, better and scalable minikube ;-)

Reply on news.ycombinator.com