2 ms·

I'm interested in hearing pros/cons of Deis vs Kubernetes. The primary disadvantage I can see for Deis is that it can only deploy single Docker containers (vs

I'm interested in hearing pros/cons of Deis vs Kubernetes. The primary disadvantage I can see for Deis is that it can only deploy single Docker containers (vs Kubernetes pods). Given the Heroku-style setup it makes sense, but it is limiting for more complex applications. On the other hand, the simplicity of Deis is attractive. I kind of wish I could use it, but I feel like it just isn't feasible for a full suite of microservices + dependencies. Regardless, congrats on 1.0!

gabrtv 12y ago
Deis and Kubernetes are solving different problems. Deis is a PaaS that provides a developer self-service capability a la Heroku. Kubernetes is a declarative container manager that provides lower-level orchestration features. Both are complimentary. For example, Red Hat is using Kubernetes to deliver their OpenShift v3 PaaS. We've explored a similar integration with Kubernetes but are currently more focused on integrating with Mesos a next step.
bacongobbler 12y ago
We hear this conversation quite a bit. Kubernetes is not a competitor to Deis. Kubernetes is a container cluster manager; a scheduler, if you will. You give it a container and some desired state and it will schedule it out to a cluster of nodes. Deis utilizes schedulers to deploy apps. We currently support Fleet at the moment but we have attended a few mesos hackathons to get a PoC working with Deis as well as kubernetes. If you have a use case, we'd be happy to hear it in the mailing list or in a github issue as a proposal :)