The host firewall currently doesn't work with portmap chaining when using kube-proxy. This limitation is related to the fact that we redirect traffic from pods to remote nodes through a tunnel when the host firewall is enabled.
Setting both global.hostFirewall=true and global.cni.chainingMode=portmap results in connection breakage, probably due to some masquerading issue. Packets are not dropped by the host firewall itself (i.e., it fails even with an allow-all policy).
The host firewall currently doesn't work with portmap chaining when using kube-proxy. This limitation is related to the fact that we redirect traffic from pods to remote nodes through a tunnel when the host firewall is enabled.
Setting both
global.hostFirewall=true
andglobal.cni.chainingMode=portmap
results in connection breakage, probably due to some masquerading issue. Packets are not dropped by the host firewall itself (i.e., it fails even with an allow-all policy).To reproduce the bug, one can comment the following line in e2e tests: https://github.com/cilium/cilium/blob/f55ec9066e3a23461a0d14e20b3be8ab49a04c97/test/k8sT/Conformance.go#L79
Related: #12345.