Skip to content
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

feat(alpine): revert 3.19 -> 3.18 #1678

Merged
merged 1 commit into from
May 27, 2024
Merged

feat(alpine): revert 3.19 -> 3.18 #1678

merged 1 commit into from
May 27, 2024

Conversation

aauren
Copy link
Collaborator

@aauren aauren commented May 27, 2024

@mrueg

Revert because of issue with iptables v1.8.10 no longer working with -C check.

Still testing this in a local cluster to make sure that the problem doesn't re-occur. Long term, this needs to be chased down with upstream netfilter, but for now this should at least help us get to a stable version of kube-router on the v2.x release line.

Fixes: #1676

Revert because of issue with iptables v1.8.10 no longer working with -C
check.
@TPXP
Copy link

TPXP commented May 27, 2024

Thanks a lot for taking the time to investigate and finding the root cause 🙌

Some nodes of our clusters run Linux 6.2, and we saw some issues with iptables failing on these kernels.

E0522 07:41:48.172118 1 network_policy_controller.go:259] Aborting sync. Failed to sync network policy chains: %!v(MISSING)ipset v7.15: Kernel and userspace incompatible: settype hash:ip with revision 6 not supported by userspace.

I haven't thoroughly experimented with all versions so I can't say for sure which version of ipset is required - I think kube-router v2.x builds worked but, just to be sure, you may want to test your build against these kernels as well

@aauren aauren merged commit 48a7357 into master May 27, 2024
7 checks passed
@aauren aauren deleted the revert_alpine_3.19 branch May 27, 2024 20:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

kube-router duplicates rules in the KUBE-ROUTER-INPUT chain
3 participants