3 ms·
I have a simple service I would like to put in production. It is a simple ML code + Rest API + testing sandwich. I only have one (virtual) server to run this o
by thomasahle 9y ago
I have a simple service I would like to put in production. It is a simple ML code + Rest API + testing sandwich.
I only have one (virtual) server to run this on, but I still think Kubernetes looks really helpful, allowing me to throw new versions in test and update the production server without downtime.
Minikube is really nice to use, and everything seems to work well, however everywhere I read, I am told minikube shouldn't be used in production. Can anybody tell me if there's a reason for this? And if so what is the recommended setup for a single-node Kubernetes?
(Side question: Why does minikube run everything in a virtual machine? Doesn't that hurt performance?)
- iamwil 9y agoHuh, I've been wrapping my ML models into a flask app and deploying it as well. If you don't mind me asking, what are you using the ML model for, and what are the current suck-ass parts of deploying it?
- dosethree 9y agoYou can get what you want with capistrano and a something like unicorn taht supports no downtime deploys
- snug 9y agoKuberenetes is meant to be a self-healing always up infrastructure, if your minikube goes down, it cannot heal fast enough, and your services will go down. It is recommended to have at least 3 nodes.
- rckrd 9y agoMinikube runs in a virtual machine because its meant to be a cross platform development environment, and linux containers aren't natively supported on macOS or windows. Minikube does have a --none driver, which run on bare metal and can be used to provision a cluster on virtualized hardware, such as a CI system or a GCE instance. Why not minikube in production? Upgrades, downgrades, clean-up and maintenance. We don't offer any real guarantees on these lifecycle operations unlike a more robust setup like GKE. Disclaimer: I work on minikube