Leverage AKS for your enterprise platform: H&M’s journey
summary
H&M moves its high-traffic storefront and many migrated services onto a multi-tenant AKS platform spread across three regions, codifies guard rails and templates so teams deploy production-ready services on Day 1 not Day 90, and reports a Weekday brand rollout that reuses those templates. Platform adds intelligent workload placement and AKS cost analysis (OpenCost), a managed Prometheus + Azure Managed Grafana stack, and features like deployment safeguards, AKS Automatic, mutation policies, confidential containers and 5,000-node scale with ~83s schedulable node provisioning; GitHub Copilot scales to 700 engineers.
AI-written summary · about
chapters (19)
- 0:00H&M’s AKS platform journey
- 4:26Cloud strategy and transformation
- 6:40Fragmentation and complexity challenges
- 9:56Platform engineering for enterprise
- 13:55Multi-tenant AKS architecture
- 15:25Platform engineering team structure
- 18:03Developer experience practices
- 20:40Future plans and GenAI exploration
- 21:42Microsoft’s AKS perspective
- 23:13AKS for developer productivity
- 26:49AKS operations with Copilot
- 31:55Workload placement in Kubernetes Fleet
- 34:20AKS cost analysis
- 35:03Observability with Prometheus and Grafana
- 36:11AKS reliability improvements
- 39:23AKS usability features
- 41:50AKS security enhancements
- 42:34Governance in AKS platforms
- 43:18AKS resources and next steps
related talks
55mMoving the enterprise to Kubernetes
01h 02mLearnings from the Enterprise-level Kubernetes transformation at Elkjøp Nordic
01h 01mDevOps with Azure Kubernetes Service
01h 22mAdventures of building a multi-tenant PaaS on Microsoft Azure
25mAKS unlighted, but what about Compliancy, cost and Multi ten
35mKubernetes journey
40mScaling Startup for Success: Building modern Architectures and Developer Acceleration
26mIf You Build It, They Will Come - a Platform Modernization Journey