How can you want to like something if you don't know what it does?

I feel similarly to the GP. I'm interested in PaaS solutions and have had successes with Keberenetes. If this filled some of the gaps in the PaaS space for me, then I'd be really interested.

There are conveniences that a proper PaaS could provide on top of Kubernetes, e.g. Heroku's deploy-on-Git-push feature. I just don't know if that's the kind of thing this project is targeted at.

OpenShift 3 also provides deploy-on-git-push on top of Kubernetes, HTTP[S] routing (uses Haproxy), and a not-bad web console. https://github.com/openshift/origin, https://docs.openshift.org/latest/welcome/index.html

Don't know alternatives well enough to compare. Disclaimer: I work at Red Hat on manageiq/openshift integration.

Tsuru.io is an open source PaaS that provides heroku like deployments and other features!

Lots of services, easy to try (just one command: https://github.com/tsuru/tsuru-bootstrap), support docker clusters(pools), auto scale, metrics, in production using docker since the beginning (about 2 years).

Agree. Tsuru is a faithful implementation of Heroku's workflow, plus the Tsuru community is very friendly and responsive.

You should have a look at Deis v2. Built on Kubernetes and has push to deploy.

i.e.: if you have some bored operations engineers just twiddling their thumbs, you can totally self host a complicated solution. Assuming you have a very common, boring problem like web service hosting or object storage.

Operations loves flavor of the month tools under active development, right?

Cloud Foundry can run Heroku buildpacks out of the box. Several of the bundled buildpacks in a CF release (Ruby, Python, Node, and I think Golang) are wrapped versions soft-forked from Heroku's.

The others (Java, PHP, Staticfile, Binary) were written specifically for Cloud Foundry.

Source: I worked on the CF Buildpacks team for a while.

To add to the list Flynn does all of this without the added complexity of Kubernetes.

Disclaimer: I work on Flynn