Switch from docker-compose to Kubernetes

[loomchild]

I am personally not convinced that it would be that useful, since Puffin is focusing on running small separate decentralized applications for many users, so I don't see much value brought by Kubernetes, which is a large application orchestration solution.

On the other hand Kubernetes is becoming de-facto standard software deployment technology. In addition to established players such as Helm, everyone else seems to be switching to it - Rancher, libre.sh, even Docker itself is supporting it natively. Also more and more cloud infrastructure providers now support Kubernetes natively (Google Cloud, AWS), so deploying it doesn't require managing a server anymore and is easier than installing Docker. However, the prices for running containers on EKS are still very high (similar to Joyent's Triton, which exists since a long time). It suggests there's no real support multi-tenancy, which will the price of running an app close to zero, which is the ultimate objective of containers from my point of view.

Any thoughts?

[rocketman0]

You make good points, multi-tenancy in Kubernetes would likely be a bit of a challenge. That said it is really is becoming more of a standard. I have a feeling its going to continue to increase in popularity and the more popular it becomes the more likely it is that a good solution could appear. I also think a switch to Kubernetes wouldn't necessarily be a bad idea from a scalability perspective.

[Jeeppler]

Supporting Kubernetes seems like a good idea. However, keep in mind that Kubernetes (as well as other solutions such as DC/OS) require master node(s) and in case of Kubernetes it also requires etcd nodes. In short it is a lot of overhead for a small cluster or a single server deployment. Docker compose is a good tool if you want to run docker containers on a single server (node).