unlighted, but what about Security and Multi tenancy?
summary
City of Amsterdam runs a Shared-AKS (DTAP) multi-tenant AKS platform that centralizes clusters, enforces private endpoints, and charges workloads by agent-pool allocation. Isolation uses agent-pool per workload plus namespace and Calico network policies; user‑managed identities attach to pools. Application Gateway + AGIC proved unreliable so nginx ingress is used, autoscaling and Defender for Cloud are enabled, CI/CD image scanning is still third‑party. A Microsoft review scores 84% compliance / 91% advisory and shared clusters reduce costs; most workloads stay under 50 pods.
AI-written summary · about
chapters (17)
- 0:00Introduction
- 1:23Amsterdam cloud strategy
- 3:13Cloud adoption framework
- 7:22Architecture decisions review
- 9:29Private clusters security
- 10:32Workload isolation concepts
- 12:50Security tools Azure Defender
- 14:04Monitoring container images
- 15:29Managed identities limits
- 16:32Azure policies Kubernetes
- 18:00Self-service for teams
- 20:31AKS features roadmap
- 21:55Troubleshooting VMs gateway
- 22:40Confidential computing plans
- 23:43AKS deployment lessons
- 24:27Cost and adoption challenges
- 25:10Q&A
related talks
25mAKS unlighted, but what about Compliancy, cost and Multi ten
29mManaging a Multi-Tenanted Kubernetes Cluster in Production
05mLightning Talk: What Makes a Good Multi-tenant Kubernetes Solution?
31mUnity in Diversity: Architecting “Shared-Fir...
29mNavigating the Multitenancy Maze: Avoiding Kubernetes Antipattern Pitfalls
25mWhat We Learned Securing AI Agents at Scale on Multi-Tenant Kubernetes Clusters
26mMulti-Tenant vs Micro-Clusters in Kubernetes-Driven Platform Engineering
33mSpace Invaders for Kubernetes: Consolidating 50 Clusters at Scale