4 ms·
FWIW, I did a comparison of k8s in Docker, KinD, and minikube last week ... https://seroter.wordpress.com/2020/03/10/lets-look-at-your-options-for-local-develop
by richards 7y ago
FWIW, I did a comparison of k8s in Docker, KinD, and minikube last week ... https://seroter.wordpress.com/2020/03/10/lets-look-at-your-options-for-local-development-with-kubernetes/ https://seroter.wordpress.com/2020/03/10/lets-look-at-your-o...
- greyskull 7y agoRead through it. Do you have a sort of TL;DR summary of pros/cons? A matrix I can use to make a decision as a new k8s user.
- richards 7y agoGood suggestion. For me, use Docker if you want k8s started up every time you start Docker, and easy ingress. I don't love having a cluster always running, so I'm keeping the k8s function off by default. Use kind if you want multi-node clusters, and a production-like simulation of your environment. Use minikube for a straightforward dev experience, where you have control over k8s version, resource allocation, and don't need meaningful configuration of the control plane.
- mleonhard 7y agoI really wish you had used a regular service definition when testing KinD. The omission reduces the usefulness of your comparison. I want to choose a local k8s cluster that is as close to production as possible. And I want my local deployment configs to be as close as possible to production. You say that "ingress in kind is a little trickier than in the above platforms" with no explanation. I feel disappointed and frustrated. :(
- richards 7y agoSure. I cheated. I specifically didn't feel like setting up extraPortMappings (https://github.com/kubernetes-sigs/kind/issues/808 https://github.com/kubernetes-sigs/kind/issues/808), and then create an ingress controller (https://kind.sigs.k8s.io/docs/user/ingress/ https://kind.sigs.k8s.io/docs/user/ingress/). Not difficult, just not turnkey availability like the other two.