Docker Fully Embraces Kubernetes
Over the past few years, Docker set out to build its own container management and orchestration layer. It’s been a positively essential part of the company’s roadmap, and one that most investors saw as the end-game play to bring in enterprise buyers at high dollar amounts. That vision changed drastically, today, when the company announced that it would be bringing Kubernetes into its enterprise platform.
At DockerCon Europe in Copenhagen, today, it was the Kubernetes open source container orchestration engine that was front and center. Google first developed Kubernetes, which is now managed by the Cloud Native Computing Foundation. Now Docker will be including Kubernetes 1.8 in its current Docker Enterprise Edition.
Previously, Docker had pushed its own Swarm as the solution to many orchestration woes, but with the announcement that it will now be offering and supporting Kubernetes, many of those Swarm capabilities are now touted as value-adds above Kubernetes.
Demo shows Community Edition running Kubernetes. #DockerCon pic.twitter.com/HVP343SJxl
— The New Stack (@thenewstack) October 17, 2017
Another Docker-Kubernetes demo using shared resources. #dockercon pic.twitter.com/Rt1RqJytvh
— The New Stack (@thenewstack) October 17, 2017
“We’re embracing Kubernetes into our product line. We’re bringing Kubernetes into Docker Enterprise Edition as a first-class orchestrator right alongside Docker Swarm,” said Scott Johnston, Docker Chief Operating Officer. He also noted that Kubernetes would be folded into the company’s desktop Windows and Mac products.”
Previously, Swarm was advertised as a cluster manager, stopping short of being called an entire cloud orchestration system. The combination of Swarm and Kubernetes allows for the inclusion of Swarm manager nodes and Kubernetes Master nodes together to enable high availability and security within deployed systems.
Johnston said this was largely done in response to customer requests for Kubernetes. “This also brings capabilities to Kubernetes we don’t see in other distributions. It enables users to take advantage of Swarms security features at the node and cluster level. Also, Docker Enterprise Edition users can manage Windows and Linux workloads through the same pane of glass,” said Johnston.
This is not a wrapper, this is not a fork. It's a full integration, says @solomonstre about Kubernetes. pic.twitter.com/tWy9hmDGUu
— The New Stack (@thenewstack) October 17, 2017
This is a major point of differentiation for Docker, and one that it has been working on ever since it first partnered with Microsoft in 2016. Docker signed on to bring its container runtime into Microsoft’s Azure cloud platform at that time, but what we didn’t quite see back then was just how much the Windows platform would gain Docker support. This announcement shows that Docker sees Windows as a standard desktop development environment for enterprise developers.
Johnston said that users will be able to pick and choose between orchestration capabilities independently. “The Kubernetes interface will be available to users that want to start with that, and available natively. We’re not wrapping Kubernetes or forking Kubernetes. This is the plain, vanilla version from the project. Customers interested in starting with that as an orchestration layer can go right at it. Meanwhile, our hundreds of current enterprise customers will continue to enjoy the benefits of Swarm. We’re not telling customers to do one way or the other as much as giving them choice,” said Johnston.
Going forward, Kubernetes will be updated to the most recent stable version every six months, said Johnston. This will begin with version 1.8 included in Docker Enterprise Edition today, with the next stable release being adopted into the platform whenever its available on the twice-yearly Docker Enterprise Edition release schedule.
For desktop users, who typically utilize Docker for development environment-based testing setups, the Windows and Mac versions of the platform will likely integrate Kubernetes directly from the master, ensuring new features are available for developers in a timely fashion, without bringing possible complications to the mainline production platform.
When asked about the company’s plans for contributing back to Kubernetes, Johnston pointed out that Docker creator and founder Solomon Hykes is already on the technical steering committee of the CNCF, the non-profit group which, in addition to stewarding Kubernetes, is also managing Linkerd, containerd, and other popular container-focused open source infrastructure projects. “[Solomon was a] founding member,” said Johnston. “We’ve been contributing to several projects around CNCF: containerd and runc. We’re already active. With this announcement, that’s going to continue and accelerate. We intend to be first class citizens and participate as full class members.”
“Our vendor’ed Kubernetes,” said Johnston, “Takes advantage of the infrastructure investments we’ve made with Swarm: the security of the individual nodes in the cluster. We’ve made security at the base of Kubernetes best-in-class. We’ve also made it very easy to install, configure, and standup Kubernetes. Kubernetes doesn’t make a lot of assumptions about the underlying cluster, so users are left to that. We’ve made it one command to set up the cluster, the security around the cluster, and on the nodes.”
@mfdii gives us the hot take on the #dockercon keynote. https://t.co/U9VgELNtT9
— The New Stack (@thenewstack) October 17, 2017
While this is a welcome addition for customers, it is indicative of a slight direction change over time for Docker.
“Maybe it’s also a reflection that we were young in the enterprise three years ago. As we’ve grown into the enterprise, we’ve seen the security requirement grow further and further. That’s increased our own investment in those feature sets. I would say it’s consistent for us, but three years ago most enterprises were kicking the tires on containers. Now you do see enterprises wanting to move their first, maybe second and third workloads into the cloud with Docker. When you do that, your security requirements become table stakes,” said Johnston.
He added that much of the security work inside Docker Enterprise Edition was performed by a security team the company acquired from Square three years ago. That team has remained together inside Docker, where it’s worked to improve the platform’s overall security model, and continues to do so, said Johnston.
The company’s DockerCon Europe continue through the rest of this week, with further announcements scheduled for tomorrow’s keynote, as well.
