Rastislav Szabo

iptables diff before node reboot (broken pod communication) vs after node reboot (issue resolved): ``` 1c1 < # Generated by iptables-save v1.8.7 on Wed Mar 16 07:49:08 2022 --- >...

> This seems to suggest that calico/node is working with out-of-date information. Are you calico/node pods "Ready"? Yes, all calico-node pods were running fine - not reporting any issues, not...

Right, I can also confirm that the issue is present on v3.22.1 as well.

> ``` > Chain cali-from-wl-dispatch (2 references) > pkts bytes target prot opt in out source destination > 1634 135K cali-fw-cali0eacf697eec all -- cali0eacf697eec * 0.0.0.0/0 0.0.0.0/0 [goto] /* cali:jfxMCpNf8Nj1KM-K...

Rocky Linux release 8.5 (Green Obsidian) also seems to be affected

Setting `FELIX_IPTABLESBACKEND` to NFT resolved the issue for us as well. What are the potential risks of forcing NFT backend?

Hey, what is the status of this issue? Recently we managed to reproduce this issue also on Ubuntu 22.04

/lgtm /approve

/lgtm /approve

/test