Windows Mesh Expansion (WME) with Linkerd

When you mesh your Kubernetes services, you get automatic mTLS, authorization policy enforcement and golden metrics. But what about your Windows servers running your legacy and line-of-business apps? Can they benefit from all the service mesh magic? 

Yes! With Windows mesh expansion (part of Buoyant Enterprise for Linkerd), you can. It pulls Windows VMs and bare-metal hosts into your Linkerd mesh and you get all of the Linkerd goodness wherever those machines run, whether on-prem or in the cloud. Behind it all is a Windows kernel-mode driver that transparently redirects traffic through the Linkerd proxy, Microsoft WHQL-signed for Windows Server so it runs on production machines out of the box. In this Service Mesh Academy, we'll go under the hood on how it works. Join us to see what a truly Windows-inclusive mesh looks like!

• Learn how Windows mesh expansion extends your Linkerd mesh to Windows workloads outside Kubernetes, on VMs or bare metal Windows Hosts, powered by a Microsoft WHQL-signed kernel-mode driver that transparently redirects traffic through the Linkerd proxy
• See how the MSI installer joins a Windows host to the mesh, and how its configuration settings control traffic redirection, identity, and proxy behavior
• Know how to onboard a Windows host into your own mesh and enforce authorization policy on its traffic, giving it the same mTLS, policy, and observability your pods already get