AKS unlighted, but what about Compliancy, cost and Multi ten
summary
City of Amsterdam runs four AKS clusters with per-team subscriptions, per-team agent-pool multi-tenancy and one shared ACR; teams get a namespaced service account, 251 IPs per agent pool (expandable), autoscaling and labeled VMs. Platform enforces Azure policies, uses private clusters and private endpoints, chose NGINX ingress over AGIC, uses Anchore for container scanning and just-enabled workload identity GA. Well-architected review scores 91. Main pain points are tenant isolation, preview vs GA limits and slow team adoption.
AI-written summary · about
chapters (7)
- 0:00Amsterdam’s AKS journey
- 2:55IT challenges and goals
- 7:14Multi-tenancy and compliance
- 10:01AKS security design
- 13:55Solution overview
- 17:33Lessons learned
- 23:21Key takeaways and future
related talks
31munlighted, but what about Security and Multi tenancy?
16mCracking the code: AI workloads at scale on AKS
01h 02mAKS Survival Pack: what to consider before going all-in with AKS
45mLeverage AKS for your enterprise platform: H&M’s journey
47mUnleashing the Potential of Hybrid Cloud
01h 01mDevOps with Azure Kubernetes Service
29mNavigating the Multitenancy Maze: Avoiding Kubernetes Antipattern Pitfalls
37mModern Architecture in the Cloud of 2026