At my company, we've set up our own Kubernetes cluster and moved our production applications over to it over the past couple months. While I definitely agree, there is a steep learning curve for getting Kubernetes set up and configured, there are several factually inaccurate things in this article.

> With Docker we were supposed not to have installation instructions (aside from a few docker run arguments). We were supposed to run containers. Swarm fulfils that promise and Kubernetes doesn’t.

We run Kubernetes on CoreOS and every piece runs in a container. On the master, the api-server, controller and scheduler all run in docker containers. On the minions, the proxy and kubelet both run in containers.

> Another thing I dislike about Kubernetes is its need to know things in advance, before the setup. You need to tell it the addresses of all your nodes, which role each of them has, how many minions there are in the cluster and so on.

The master does not need to know the these things. Minions do need to know the address of the master, but they can self-register with master and join the cluster anytime.

With that being said, it did take two of our senior devs over a week to get a cluster we were happy with. I'm a fan of docker compose, and hope swarm becomes a good competitor to Kubernetes. I don't think it's there yet though.