Taylor Brown

Announcing the Windows Server Annual Channel for Containers techcommunity.microsoft.com/t5/windows-ser… Happy to answer your question on this announcement! #WindowsContainers #Docker #Kubernetes #K8s #AzOps

@elonmusk And I’ll now be moving fully off this platform untill it’s not run by @elonmusk. You have broken many promises and proven incompetent as a leader. Hopefully twitter survives without you.

Should I step down as head of Twitter? I will abide by the results of this poll.

I'll post links to the other positions as the hiring managers get them posted and when we get the next batch.

We are hiring for Windows containers! I have a PM position on my team, a PM position working on Windows container networking and multiple engineering positions with more expected soon :). Here is the link to the PM position on my team: careers.microsoft.com/us/en/job/1498…

I am not fully migrating (yet) but intend to dual post and may fully migrate in the future. #Mastodon here @thecloudtaylor" target="_blank" rel="nofollow noopener">mastodon.social/@thecloudtaylor #TwitterMigration

This is a great talk on Windows containers. Thank you Julian and @RelativityHQ! youtu.be/LxVcNXu04eg

If you are interested in helping shape how windows container images are distributed (foreign layers etc...) please continue to this discussion github.com/microsoft/Wind…

@awakecoding @justincormack We’re continuing to invest a lot in containerd (more coming) I think a lot could be built on that layer. But the highest roi has been k8. There are so many apps to modernize to cloud/hybrid.

@Taylorb_msft @justincormack Is there still a future for Windows containers without AKS HCI and the whole orchestration layer? I still feel the biggest tragedy is missing out on running Windows containers as regular system services - everything is already there, it just needs to be nicely integrated together

@awakecoding @justincormack Don’t rule it out - but it’s a lot harder than it first appears.

@awakecoding @justincormack We did a small hack of a windows kvm vm on Linux, but there are a lot of issues. K8 doesn’t know about nesting, how does aqua or other security tools work? What about networking? It got super complicated.

@awakecoding @justincormack So far we’ve felt that doubling down on making windows containers awesome in the ecosystem is the win. So we’re moving even more engineering people onto windows containers. And we’ll keep listening and working on licensing changes that make since.

@awakecoding @justincormack The former has perf/density/observability/ecosystem issues, the latter has major compatibility issues plus ecosystem challenges. Certainly not out of the realm of possibility long term but it’s not clear what the real customer benefits are ultimately.

We are getting ready to move… our current house has asymmetrical 1gb fiber but the new house is in an older neighborhood on cable 😢. New house is overall a major improvement except internet. How real is docsis 4? I fear fiber is a ways away there.

@awakecoding @justincormack Another one that feels easy until you start prototyping and thinking through all the details.

@awakecoding @justincormack Yes. But it’s not simple. And it’s not a small investment. How does networking work? How about pv’s? Or side cars? Licensing is also an obvious consideration, but that’s actually easier to workout than the experience questions.

@justincormack And by us I mean the larger community. OCI + CNCF etc. from a Microsoft perspective we simply want more customers to benefit from windows containers.

@justincormack I thought it was a slam dunk to remove them as well… but as we started to make that change we got feedback about their value. Specifically around pushing from devs and ci/cd that wasn’t insignificant. Ultimately customers need to help us decide.