-
Notifications
You must be signed in to change notification settings - Fork 499
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Traffic-agent using incompatible iptables-variant (legacy instead of nft) #3542
Comments
Thanks, @glooms . That's a great bit of feedback and a fix. Much appreciated. |
Hi @glooms , do you recall what error you got when running into this? It would be great to know if you still have access to that or remember what you first saw. |
Hello @cindymullins-dw, the error I get is that the init-container created when doing
|
My cluster worker nodes having the same issue as well after we upgraded the Kernel version from 4.19.91 to 5.10.134 |
The OS we're using for our clusters
AlmaLinux 9.1
doesn't supportiptables-legacy
, onlyiptables-nft
, which surfaced as an unintelligible error asking us to update the kernel.The fix was quite simple, we just did a derivative of the
Dockerfile.traffic
where we symlinkiptables
to/sbin/xtables-nft-multi
(whatiptables
was originally pointing to), like so:Albeit the fix is quite simple it was very hard to find so it might be good to solve it or at the very least to add it to your troubleshooting section as it might be useful for others.
The text was updated successfully, but these errors were encountered: