3 ms·
I personally use minikube[0] to have local deployments and production deployments to be very similar. Minikube is your personal kubernetes, and it's very to us
by jiehong 5y ago
I personally use minikube[0] to have local deployments and production deployments to be very similar.
Minikube is your personal kubernetes, and it's very to use, and is very close to the production kubernetes, but on a single node.
I don't see enough praise for minikube on HN, but I think it's deserved.
Albeit, you cannot do a "docker-compose up --build", but instead "docker-compose build && kub apply -f <template.yaml>", which is equally fast IMO.
[0]: https://minikube.sigs.k8s.io/docs/ https://minikube.sigs.k8s.io/docs/
- husarcik 5y agoAh, interesting! Any downsides to this you've run into?
- driton 5y agoIt's been a few years since I tried using it, so take this with a grain of salt, but my biggest gripe with it was that it would grind my computer (a beefy Dell) to a halt. Of course, this depends on what sort of environment you're trying to replicate. If it's 2 to 3 microservices and a database, I would imagine it's fine, but anything more, which is what I had to deal with at the time, it was a no-go. Especially so since this meant that running minikube and having a RAM-thirsty IDE, like Intellij IDEA, was practically impossible.
- EricLeer 5y agoRam usage is a lot better when using docker as a driver instead of a vm, which immediately reserves all memory you give it. see https://minikube.sigs.k8s.io/docs/drivers/ https://minikube.sigs.k8s.io/docs/drivers/ for more info