tsuru 1.3.0 released, with Kubernetes support!
We recently released tsuru version 1.3.0. This version adds experimental support to using Kubernetes as a provisioner.
Until version 1.1.x, tsuru only supported one provisioner: Docker. That means we could only run apps on top of Docker clusters. In version 1.2.0, we started supporting Swarm clusters. Each pool is associated to a provisioner, so you could have a Docker pool and a Swarm pool at the same time. And now, tsuru also supports Kubernetes.
Kubernetes is a container orchestration solution that's been growing very fast. It's already one of the most active open source projects, and it's being used by many companies, like Github, Wikimedia and Niantic (creator of Pokemon Go). It was an obvious solution to decide supporting it as a provisioner. If you run your tsuru installation in Google Cloud Platform, you could use Google Container Engine (GKE) to start a Kubernetes cluster and register it in tsuru.
Why not replace tsuru with Kubernetes?
A question we hear a lot is: why should I use tsuru and not Kubernetes? Our answer is: why not use both?
Kubernetes is an amazing solution for container scheduling and orchestration. It's production ready, and it's getting better each day. But managing your own Kubernetes cluster directly can be very hard.
Developers that already use tsuru to manage their apps know how easy it is to create apps, make deploys, check logs, manage services, etc. Kubernetes introduce a lot of other concepts and abstractions. What we did was mapping these concepts to the current tsuru architecture — actually, we created a new concept of cluster, which is also used with Swarm.
This means that, as a tsuru user, nothing changes in the way you manage your apps. tsuru takes care of the details and complexities for you, and you get all the benefits from Kubernetes.
Notice that Kubernetes support is still experimental. If you decide to try it, be aware that you may find bugs. If you do, please open a new issue in tsuru.
There are other important new features in this release. For more details, check the full release notes.
