Kubernetes Ecosystem in Azure
summary
Azure Security Center flags a wide API-exposure issue and detects a pod accessing a sensitive host volume, offering remediation links; secrets are mounted from Azure Key Vault into pods via the CSI Secret Store Driver and authenticated with aad-pod-identity, appearing as files that can be cat'ed. Azure Policy embeds OPA with built-in policies (example: deny external LoadBalancer or set to audit), running compliance checks every 15 minutes and reporting a noncompliant external LB. Advisor suggests pod disruption budgets and AKS diagnostics surfaces killed or OOM-restarting pods. Azure Arc connects a local kind cluster, deploys flux to create namespaces from Git within minutes and keeps them in sync.
AI-written summary · about
chapters (6)
- 0:00Introduction
- 0:54Azure Security Center
- 2:05Secret Store Driver
- 4:39Azure Policy
- 8:56Azure Advisor
- 11:25Getoffs
related talks
32mMastering Cloud Kubernetes: Navigating Azure's Kubernetes Service Maze
36mDeep Dive: Azure SIG
33mIdentity and Access Management in Kubernetes
01h 01mLearn Live: Introduction to Azure Arc-enabled Kubernetes
35mIntro + Deep Dive: Azure SIG
24mOne stop talk for kubernetes security !!
43mSecuring container deployments on Azure Kubernetes Service with open-source tools
28mHow to Use AKS Pod Identity with Vault