Cilium fails to start with IPv6 on v1.13.0 #13268
-
|
I've recreated my dual stack cluster with v1.13.0 but Cilium v1.19.2 is failing to start with: but the weird thing is, v1.13.0-beta.1 was working fine. It also works with v1.12.7. Has something changed here? I don't see anything obvious in the release notes/commit diffs. I'm also seeing: |
Beta Was this translation helpful? Give feedback.
Replies: 4 comments 5 replies
-
|
Not sure, but feels like a bug in Cilium, it is not compatible with modern iptables. Cilium should use nftables actually. |
Beta Was this translation helpful? Give feedback.
-
|
I have same issue with dual-stack mode |
Beta Was this translation helpful? Give feedback.
-
|
Are you using |
Beta Was this translation helpful? Give feedback.
-
|
I see the same issue when upgrading Talos from 1.11.6 to 1.12.7 using Cilium 1.17.3. We use IPv4/IPv6 dual stack but do not use the tailscale extension. From what I can tell it might be related to: cilium/cilium#43940 If this is indeed the case we have to wait on upgrading until Cilium version 1.20 which is planned for July or see if the Cilium team can backport the fix to 1.19. |
Beta Was this translation helpful? Give feedback.
Thanks for confirming, yes, the real bug is that tailscale was stripped off the
iptablesbinaries in 1.13, and it falls back to native nft mode (which is not bad), but Cilium still can't do native nft, so it tries iptables-over-nft and it leads to a conflict.The workaround is to downgrade for now, or remove tailscale. We will ship a fix in 1.13.1