-
Notifications
You must be signed in to change notification settings - Fork 522
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
v1.26.2 - kube-proxy - Failed to execute iptables-restore - unknown option "--xor-mark" #4295
Comments
Thanks for the detailed report. I'm working on reproducing the issue now. Will update once I have more information. |
Update: I have just recreated the error and confirmed the reason. There's an issue with kernel 5.15 which uses k8s from 1.24 - 1.27, which causes it to be incompatible with IPv6. We are currently working on fixing it and appreciate your patience. |
Bottlerocket team became aware of an issue impacting K8s 1.24-1.27 AMI from version 1.26.2 and version 1.27.0 running kernel 5.15.*. The issue manifest in all nodes using IPv6 on these variants failing due to broken ip6tables commands needed to configure the node. Bottlerocket versions earlier 1.26.2 as well as Bottlerocket variants for K8s 1.28 and above are not impacted. Bottlerocket team is working on releasing the fix. In the meantime, if you are using K8s 1.24-1.27 and you need to use IPv6, please use Bottlerocket version 1.26.1. |
I have a fix for this in PR here bottlerocket-os/bottlerocket-core-kit#266. Thanks for the report @MrFishFinger! |
This should be fixed in Bottlerocket 1.27.1 which should be fully released shortly. Here is the tracking issue for 1.27.1: #4303 |
Closing this issue since 1.27.1 is out and fixes this issue. |
I'm sorry, I'm not a Bottlerocket user, but the same error occur in my KinD environment, so please let me ask. Node docker image : kindest/node:v1.32.0
Please teach me the way to confirm if this problem is fixed in not-Bottlerocket k8s environment. |
Hello @yushoyamaguchi , the problem we had was that the kernel 5.15.168 (what we used at the time ) was the culprit. To fix this, we carried on a patch that was included in 5.15.170: So if you are experiencing a similar problem, you have to either port back the patch (similar to what we did to address the problem), or just move to >= 5.15.170. |
@arnaldo2792 |
Image I'm using:
v1.26.2 (linux kernel 5.15.168)
What I expected to happen:
kube-proxy to operate without errors
What actually happened:
kube-proxy repeatedly throws the error:
How to reproduce the problem:
NOTE: rolling back to image "v1.26.1" (using linux kernel 5.15.167) fixes the issue.
details from 1.26.2 node with issue:
info from 1.26.1 node without issue:
The text was updated successfully, but these errors were encountered: