Deis to Join Microsoft

Congrats to Gabe and the whole Deis team on the acquisition.<p>For folks not familiar with Helm, it&#x27;s basically apt-get for Kubernetes, but with the ability to deploy complex multi-tier systems. It has now graduated out of the Kubernetes incubator.<p>And their Workflow product (also open source), is basically the smallest piece of software that lets you run Heroku buildpacks on top of Kubernetes. So, you can get a 12-factor PaaS workflow, and still have the full Kubernetes API underneath if and when you need it.<p>Update: And I left out my all-time favorite piece of marketing collateral, their Children&#x27;s Illustrated Guide to Kubernetes (available both as children&#x27;s book and video): <a href="https:&#x2F;&#x2F;deis.com&#x2F;blog&#x2F;2016&#x2F;kubernetes-illustrated-guide&#x2F;" rel="nofollow">https:&#x2F;&#x2F;deis.com&#x2F;blog&#x2F;2016&#x2F;kubernetes-illustrated-guide&#x2F;</a><p>(Disclosure: I&#x27;m the executive director of CNCF and Gabe has been a super valuable member.)

The industry is consolidating around the Kubernetes ecosystem. This acquisition is an example of many others that will follow as the major players want to build up their offerings and expertise.

Every time someone is acquired by Microsoft I can&#x27;t avoid feeling sad for them.<p>It&#x27;s true they&#x27;ll get a decent amount of money, that, from now on, they have infinitely deep pockets, that they&#x27;ll have some of the best keyboards and mice, but it&#x27;s also true their wiki will end up in Sharepoint and their e-mails in Exchange.

Wait what? Didn&#x27;t the Deis team just join EngineYard last year? Furthermore, why would Microsoft want Deis? They haven&#x27;t really shown an interest in Kubernetes thus far.

I&#x27;m really curious how people administer their K8S clusters for installation, upgrades, etc.<p>I&#x27;m very familiar with docker, which we&#x27;ve been using for over 2 years. But now, we&#x27;re trying to get k8s running, with either kargo, kubeadm, deb packages, etc.: They all failed with different bugs on different set of clouds &#x2F; settings. (Trying to stick to running it on Ubuntu xenial).<p>Not sure if it&#x27;s because 1.6.* just came out of the oven when I started...?<p>Thanks to Minikube, I understand how powerful k8s can be, and actually find kubectl quite simple to use, but I&#x27;m confused by how fragile and complex installation and setup seems to be. I&#x27;m unsure how someone is supposed to maintain this system considering how (overly?) modular it is and the bugs I&#x27;ve encountered. Knowing that docker has a LOT of bugs, and k8s builds on top of it, I&#x27;m a bit scared. And there is no clean documentation on how to install it, with sections for all your choices, in a generic&#x2F;agnostic way (deb+rpm distros, cloud integration or simple abstract VMs, ...)<p>What is you workflow? :)

I really hope Microsoft doesn&#x27;t hurt this. For example, there are great docs for AWS and Google, but given the way they&#x27;ve ruined Skype, I really hope they don&#x27;t turn this into some kind of Azure-focused system while dropping support for AWS, etc. Congrats to the awesome Deis team -- let&#x27;s just hope that Microsoft doesn&#x27;t just run it into the ground when it comes to non-Azure platforms.

Congratulations Gabriel! Having worked on containers space in Microsoft Azure before, my opinion is that this is a great move by Microsoft. In the past years, I&#x27;ve seen the company struggle in finding great talent in OSS&#x2F;Linux stack. Simply, there are a lot of areas Microsoft could expand, but there is not enough talent. Deis will definitely take a ton of expertise in open source software and community to Microsoft. Now that Kubernetes is a big part of Azure’s container service, Deis brings a lot of fresh blood to Microsoft. I hope it works out great for both companies (and the open source Kubernetes community).

I&#x27;m somewhat surprised. Why would Microsoft put weight into Deis vs use something like Kubernetes or Mesos? I haven&#x27;t kept up with Deis&#x27;s growth and I&#x27;m obviously very happy for them, but I&#x27;m curious what the gain is. Based on HN posts and other devops forums, Kubernetes eeems to have gained a lot of momentum recently.

Deis has changed a lot since I last looked at them. They&#x27;ve dropped their original PaaS and developed an ecosystem on top of Kubernetes. Microsoft has been showing a lot of interest in Docker, so can see why this acquisition would make sense for them.

&quot;Microsoft has a storied history of building tools and technologies that work for developers.&quot;<p>I&#x27;m not sure how I feel about that statement.

Does this mean a commitment of Microsoft on k8s ecosystems or simply a talent acquisition or both?

Congrats to the Deis team! I was an early adopter and the team was just fantastic at answering questions, implementing feature requests and resolving issues on GitHub.<p>PS: I&#x27;ll take this opportunity to shamelessly promote my web based Deis UI: <a href="http:&#x2F;&#x2F;github.com&#x2F;olalonde&#x2F;deisdash" rel="nofollow">http:&#x2F;&#x2F;github.com&#x2F;olalonde&#x2F;deisdash</a>

Congrats on the acquisition, I&#x27;m just sad I can&#x27;t be there to congratulate you.

What!? I never would have expected this, quite a surprise. I hope it works out for them.

If Deis was that valuable, one could assume that EY agreed to this arrangement because they are low on cash and needed the money.<p>How often is a company, in effect, acquired twice?

Love Deis, we have used V1 and V2 (with kubernetes) at my current job with success, but also had weird stability and reliability issues from time to time.

The Deis team was extremely helpful over IRC when I was building on top of their PaaS. Great team and culture, Microsoft is lucky to have them.

Well, that&#x27;s definitely a way to buy yourself into the Kubernetes ecosystems. Congratulations to the Deis team!

Congratulations to the Deis Team. It&#x27;s been a pleasure working with them on the Helm project.

Next week, Flynn to Join Apple.<p>Let the PaaS arms race begin.