You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was surprised to see that the rules for the first host port were added correctly whereas the rules for the remaining host ports were said to already exist. Manually issuing the ip6tables commands seems to confirm the issue. There’s an open ip6tables bug report describing the problem: https://bugzilla.netfilter.org/show_bug.cgi?id=1667.
The text was updated successfully, but these errors were encountered:
Hi, thanks for the report and all your debugging work so far! This has been helpful in pinpointing the issue which indeed is caused by a commit introduced in iptables v1.8.9 (eb2546a84677, where the call to make_delete_mask in check_entry should pass sizeof(*fw) instead of sizeof(fw)). I will prepare a patch and propose it upstream.
Image I'm using:
BOTTLEROCKET_x86_64 1.13.1-32e9bb46 AMI on EKS managed node group.
What I expected to happen:
Pod host ports working.
What actually happened:
Only the first host port of the pod is working.
How to reproduce the problem:
On an EKS IPv6 cluster with a Bottlerocket node group, deploy a pod with several host ports. Only the first host port will work.
After tracking down the issue to missing iptables rules, I ended up instrumenting the portmap CNI plugin binary with logs in this function https://github.com/containernetworking/plugins/blob/8813bfea7b706ee02acfa9687369c7ce0983bf02/pkg/utils/iptables.go#L125:
I was surprised to see that the rules for the first host port were added correctly whereas the rules for the remaining host ports were said to already exist. Manually issuing the ip6tables commands seems to confirm the issue. There’s an open ip6tables bug report describing the problem: https://bugzilla.netfilter.org/show_bug.cgi?id=1667.
The text was updated successfully, but these errors were encountered: