A Case Study for Improving Network Isolation in a Multitenant Kubernetes Cluster

on YouTube ↗32m

" summary

Case study shows a working solution to give tenant pods private interfaces in a shared AKS cluster using KEP-3698 multi-network, a custom PodNetwork CRD plus a CNI extension and a device plugin that registers extra NICs to the kube-scheduler. Demo provisions pods with two IPs (infra + tenant), supports fixed IPs per pod, and proves isolation: Red pod cannot reach Blue pod and tenant VMs reach only their pod. Azure VM SKU limits apply (currently up to eight NICs).

AI-written summary · about

" chapters (4)

1. 0:00Introduction
2. 0:34Agenda
3. 15:40Demo
4. 23:22Questions

" related talks

• 37mTenant Autonomy & Isolation In Multi-Tenant Kubernetes Clusters - A Comprehensive GuideLukas Gentele · ContainerDays Conference 2024
• 35mRunning Isolated VirtualClusters With Kata & Cluster APIChris Hein, Eric Ernst · KubeCon + CloudNativeCon North America 2022
• 51mMulti-tenant KubernetesMikhail Sidorov · Saint HighLoad++ 2022
• 25mUnderstanding Isolation Levels in the Kubernetes LandscapeJiaqi Liu · KubeCon + CloudNativeCon Europe 2021
• 40mPanel Discussion: Multi-Tenancy in Kubernetes: Current State and Future RoadmapTasha Drew, Ryan Bezdicek, Sanjeev Rampal, Erica Von Buelow · KubeCon + CloudNativeCon Europe 2019
• 35mDeep Dive: Kubernetes Working Group for Multi-tenancyAdrian Ludwin, Sanjeev Rampal · KubeCon + CloudNativeCon North America 2019
• 29mManaging a Multi-Tenanted Kubernetes Cluster in ProductionJosh Bowen · KubeCon + CloudNativeCon North America 2016
• 35mMulti-Tenancy on Kubernetes with Virtual ClustersEnrico Candino · containerday 2025