Running a DevOps style production Docker cluster using the Microsoft platform

on YouTube ↗34m

" summary

Shows a live example of diagnosing a CPU-bound bug caused by a naive paging change in the leaderboard API, traced with Application Insights and OMS to a container hitting a 0.25 CPU limit. Uses Docker multistage images, CI/CD in Visual Studio Team Services, and deploys to AKS (Azure Kubernetes Service) by tokenizing a Kubernetes YAML and running kubectl apply. Demonstrates fixing code, rebuilding (build ID 99 -> 100), and rolling forward to production during the session so the site recovers.

AI-written summary · about

" chapters (11)

1. 0:00Introduction to DevOps cluster
2. 3:41Demo application overview
3. 5:06Monitoring cluster health
4. 11:35Traceability with VSTS
5. 16:17Fixing the bug locally
6. 18:43Containerizing dependencies
7. 21:11Automated CI/CD pipeline
8. 27:42Infrastructure as code
9. 29:31Chatbots for support
10. 32:01Deploying the hotfix
11. 33:08Summary and key takeaways

" related talks

• 35mRunning a DevOps Style Production Docker Cluster Using the Microsoft PlatformLoek Duys, Marcel de Vries · DevDays Europe 2019
• 49mTaking your .NET Core container solution from laptop to productionAlex Thissen · DevOps Fest 2019
• 01h 18mEmbracing Docker simplicity - while harnessing platform powerMichele Bustamante · NDC Sydney 2017
• 55mArchitecting .NET solutions in a Docker ecosystemAlex Thissen · .NET Fest 2019
• 01h 03mScaling Docker Containers using Kubernetes and Azure Container ServiceBen Hall · NDC Oslo 2017
• 01h 00mBring your ASP.NET Core solutions to Kubernetes in AzureMarco De Sanctis · DotNext 2019 Moscow
• 01h 07mDocker Containers on Azure - let me count the waysMichele Bustamante · NDC Minnesota 2018
• 40mDevOps and Kubernetes in VSTS on Azure and BeyondStas Pavlov · DelEx Conf 2018