[{"data":1,"prerenderedAt":16},["ShallowReactive",2],{"blog-tag-en-kube-router":3},[4],{"path":5,"title":6,"description":7,"date":8,"tags":9},"\u002Fblog\u002Fen\u002Fk3s-networkpolicy-dual-stack-kube-router-ipv6-gap","\"K3s Ignores NetworkPolicy\" Was a Myth. Traffic Still Leaked Through — the ServiceLB Blind Spot","K3s enforces NetworkPolicy by default via its built-in kube-router controller. Yet traffic via LoadBalancer still leaked through — the cause was ServiceLB's implementation combined with a permanent limitation of the NetworkPolicy API. Here's how to detect and fix it.","2026-09-24",[10,11,12,13,14,15],"k3s","kubernetes","networkpolicy","servicelb","kube-router","network-security",1792592711655]