AKS Survival Pack: what to consider before going all-in with AKS
summary
Azure Kubernetes Service manages the control plane but leaves worker nodes, upgrades and hardening to the user, and neglecting basics causes real incidents: missing CPU/memory limits leads to evicted pods and cluster-wide outages, container images can be 13–14 GB images that take 10–15 minutes to pull, and one study finds 37% underutilized compute in clusters. Recommendations include Azure Policy for guardrails, GitOps with caution, and cost/security tooling such as kube-cost/OpenCost; demos and GitHub playbooks illustrate fixes.
AI-written summary · about
chapters (9)
- 0:00Introduction to AKS
- 6:34Application readiness
- 13:01Human and cultural factors
- 16:07Developer experience
- 21:26GitOps and deployment
- 23:55Cost and sustainability
- 32:45Security considerations
- 44:02Operations and reliability
- 51:04Q&A and closing
related talks
33mManaged Kubernetes Service: Day Zero Survival Pack
32mMastering Cloud Kubernetes: Navigating Azure's Kubernetes Service Maze
30mManaged Kubernetes Service Day Zero Survival Pack
57mAzure Kubernetes Service (AKS) for Beginners
16mCracking the code: AI workloads at scale on AKS
56mAzure Kubernetes Services 101 for Developers
01h 01mDevOps with Azure Kubernetes Service
44mAzure Linux: A container host OS for Azure Kubernetes Service (AKS) Q&A
