Wait what? Didn't the Deis team just join EngineYard last year? Furthermore, why would Microsoft want Deis? They haven't really shown an interest in Kubernetes thus far.
Except for helping with Windows Server support for kubernetes[0] and supporting kubernetes in Azure Container Services[1]
[0]: http://blog.kubernetes.io/2016/12/windows-server-support-kub...
[1]: https://azure.microsoft.com/en-us/blog/kubernetes-now-genera...
[1] https://techcrunch.com/2017/04/10/microsoft-acquires-contain...
When the Skype buyout was announced, my friends called and laughed at me. The tech evangelist who worked for Microsoft at the time that I ran across while in Stockholm for business was super stoked.
I know and lived the days, I see the stories about the various "reporting back" -- that is outside my purview -- but when it comes to engagement with the OSS community, including Kubernetes, some simple searching will reveal just how much we've been involved in such.
One engineer working for the Azure Container Service team personally wrote most of the Azure Cloud Provider. An engineer from Redhat contributed the initial persistent volume on Azure support. An engineer in DX/TED is helping improve persistent volume support in 1.5.3 and 1.6. These things are easily revealed looking at Github PRs and other activity.
It's easy to post the "knee-jerk" post, I know I see something and think such, but sometimes a bit of searching will reveal surprises.
No cause effect on dokku. Both are separate projects managed by separate entities.
We do, however, wish them luck and are happy to see them succeed.
- Source: I am one of the primary Dokku maintainers.
Instead, we switched to running normal VMs using CoreOS and running Kubernetes on top of that. Same features and stability, but with the auto-update benefits of CoreOS.
[1] https://coreos.com/tectonic/docs/latest/install/azure/azure-...
[2] https://coreos.com/blog/tectonic-highly-available-clusters.h...