Migrate and Modernize with Kubernetes and Windows Containers
summary
Claims Kubernetes plus Windows containers let teams lift and reshape legacy Windows apps with minimal code changes, containerizing full .NET and native pieces and running them on AKS. Demo converts a 2010 Music Store sample enhanced with MSMQ, WCF, pInvoke, Windows Service, file watcher and uses Windows server core ~1GB and nano ~100MB base images, deploys to mixed Linux/Windows node pools, shows pods auto-restart and scaled replicas, and notes operational realities: images must be rebuilt after Patch Tuesday, AKS process isolation only, no Hyper‑V isolation, Azure CNI and 10‑node pool limits, and GMSA not yet supported.
AI-written summary · about
chapters (16)
- 0:00Motivation for Modernization
- 0:50App Modernization Approaches
- 2:39Comparing Migration Approaches
- 4:58Container Fundamentals
- 5:33Anatomy of a Windows Container Image
- 6:12Choosing the right image
- 9:34Architecture in Linux
- 11:36Isolation with network namespaces
- 15:10Windows Server container updates
- 24:55Kubernetes Basic Constructs
- 31:41Kubernetes with Windows Server
- 33:46Reference App Legacy
- 40:39Windows Admin Center: Creating new container images
- 48:31Common pitfalls
- 52:40Current limitations for Windows Server node poolt and AKS
- 55:28OS-level considerations
related talks
16mModernizing a legacy app using Windows Containers and Kubernetes: Challenges and Lessons learned
15mYes, Kubernetes Can Run Your Windows Apps. Seriously...
01h 01mDeploying Windows Container based apps using Kubernetes
46mDeploying Applications in Kubernetes - Windows Edition!
37mContainer Technology Drives Windows Application Transformation
29mFrom EC2 to Kubernetes Takeaways from a Brownfield Migration
01h 01mKubernetes, Azure and .NET - What's it all about?
01h 04mIntro + Deep Dive: Windows SIG