简体   繁体   English

kubernetes 中的多播隔离

[英]Multicast isolation in kubernetes

How can I isolate multicast traffic in one namespace in kubernetes.如何隔离 kubernetes 中一个命名空间中的多播流量。 Ingress policy didn't solve this, I can capture multicast traffic from different namespace.入口策略没有解决这个问题,我可以从不同的命名空间捕获多播流量。

Usually, you can use Network Policy to manage it.通常,您可以使用网络策略来管理它。

Looks like now the only one Network Provider with a support of Network Policy has the support of multicast - Weave.看起来现在唯一一个支持网络策略的网络提供商支持多播 - Weave。

But, based on its documentation , it is not possible to manage multicast rules:但是,根据其文档,无法管理多播规则:

As of version 1.9 of Weave Net, the Network Policy Controller allows all multicast traffic.从 Weave Net 1.9 版开始,网络策略控制器允许所有多播流量。 Since a single multicast address may be used by multiple pods, we cannot implement rules to isolate them individually.由于单个多播地址可能被多个 pod 使用,我们无法实施规则来单独隔离它们。 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.您可以通过在 YAML 配置中将 --allow-mcast=false 作为参数添加到 weave-npc 来关闭此行为(阻止所有多播流量)。

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM