Talk Deep Dive
summary
Kubernetes often surprises because its architecture produces expected-but-different outcomes: nodePort bypasses network policy in some CNIs so external traffic can skip cluster-level rules, observed in test clusters and varying by overlay implementation; logs and events remain separated so operators must assemble logs from multiple sources to debug; PodSecurityPolicy spends years in beta then gets deprecated — PodSecurityPolicy deprecation — leaving users scrambling for replacements. Recommendations: test behavior against your CNI, document edge cases, and expect long, complex migrations.
AI-written summary · about
chapters (4)
related talks
51mKubernetes SIG-Network: Intro and Deep-Dive
01h 28mSIG-Network Intro & Deep-Dive
46mKubernetes Policy WG Deep Dive
46mContinuous Kubernetes Security
01h 28mIntro + Deep Dive: Kubernetes (Network) SIG
48mThe Path Less Traveled: Abusing Kubernetes Defaults
46mWhat I wish I knew about Kubernetes bef…
32mUnderstand and Troubleshoot the “Magic” of Kubernetes Networking - Minhan Xia & Rohit Ramkumar
