<p>How can I isolate multicast traffic in one namespace in kubernetes. Ingress policy didn't solve this, I can capture multicast traffic from different namespace.</p>

<p>Usually, you can use <a href="https://kubernetes.io/docs/concepts/services-networking/network-policies/" rel="nofollow noreferrer">Network Policy</a> to manage it. </p>

<p>Looks like now the only one Network Provider with a support of Network Policy has the support of multicast - Weave. </p>

<p>But, based on its <a href="https://github.com/weaveworks/weave/blob/master/site/kubernetes/kube-addon.md#network-policy" rel="nofollow noreferrer">documentation</a>, it is not possible to manage multicast rules:</p>

<blockquote>
  <p>As of version 1.9 of Weave Net, the Network Policy Controller allows all multicast traffic. Since a single multicast address may be used by multiple pods, we cannot implement rules to isolate them individually. You can turn this behaviour off (block all multicast traffic) by adding --allow-mcast=false as an argument to weave-npc in the YAML configuration.</p>
</blockquote>
