As part of the deal, you get a single-node Kubernetes cluster using the latest version of Docker as the container runtime, and the ability to deploy to Kubernetes using Docker Compose or Kubernetes manifest files. Well, you can now build their containerized applications and deploy them to Kubernetes, locally and on the same Docker instance.
The announcement signified a major strategic decision by Docker, and it was followed up by the release of Docker for Mac with Kubernetes a few weeks ago. While one can argue about the unequivocal tone used in these titles, there is little doubt that 2017 was a watershed year for Kubernetes, and in many ways for Docker as well. Since Docker offers an orchestration tool of its own, Docker Swarm, this move has given rise to article titles such as “Docker give into the inevitable” or “Kubernetes has won.”
This has been somewhat of a big topic for debate in the world of containers and orchestration, and for good reason. If you just awoke from a few months worth of slumber (three months to be exact), this might be a bit of a shocker-Kubernetes? On Docker? So, yes-last October Docker announced at DockerCon Europe that future EE versions are going to support Kubernetes integration.
