4 ms·
> 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
by shlant 11y ago
> 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.
I don't think the direct complaint was that Kubernetes didn't "run in containers" but that it isn't as easy to set up as "just running some containers".
"With Docker we were supposed not to have installation instructions (aside from a few docker run arguments)". He was saying that the Kubernetes setup didn't fit the ease of setup touted by Docker.
- hosh 11y agoIt's a fair point -- Kubernetes is a pain to install. But I think the author then translated that to mean that Kubernetes is also difficult to use. It's much easier to use than it is to install. On the flip side, when I had started seriously using Docker, I quickly ran into it's limitations. Docker is easy to use... as long as you stayed within the playground. When I started using Docker Compose seriously, I quickly ran into problems it couldn't handle. This was about 12 months ago. I think the current networking and docker swarm expanded that playground ... but it doesn't bridge the gap into getting this out as reliable and resilient infrastructure.
- serverholic 11y agoI have a feeling Docker will get there eventually. It seems they are moving slower because are being very careful and deliberate with what they introduce. Docker seems to go for solutions that are general and flexible whereas kubernetes is very opinionated.
- hosh 11y agoI agree that Docker is careful about where they are going. I'm not so sure that Kubernetes is being opinionated. They sit higher in the stack, and yet, it is built as a collection of building blocks. Chances are, what Docker Swarm will turn into is reinventing Kubernetes.