Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
I'm looking forward to a time when we no longer need to configure iptables. However, for the moment there's a couple of minor features we use to handle policy and forwarding correctly which rely on iptables. Furthermore, even if all of this is implemented in eBPF, the user's environment may still have iptables configured and this can then interfere with the Cilium traffic handling, depending on how Cilium is configured. For now, it likely makes sense to warn users that disabling this flag could lead to unexpected policy and forwarding behaviour. Once we've resolved the linked issue, maybe we can think about reverting this to an info message to account for the compatibility case mentioned above. Signed-off-by: Joe Stringer <joe@cilium.io>
- Loading branch information