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
fix: Delegated ipam not configure ipv6 if ipv6 disabled in agent #31104
fix: Delegated ipam not configure ipv6 if ipv6 disabled in agent #31104
Conversation
Good catch. My suggestion would be to fix this on this line instead -- something like if ipv6IsEnabled(ipam) && conf.Addressing.IPV6 != nil { And, for extra safety, do the same for ipv4 on line 578. Make sense? |
Yep I thought about this. The reason I went with this approach is
|
Hi, I'd suggest a release note in the description like: "Fix crash of cilium-cni with delegated IPAM when IPv6 is disabled". This way users have a decent chance to understand the change and whether this fix may address a problem they are facing. |
/test |
1 similar comment
/test |
8a7cb82
to
f4dc86e
Compare
@tamilmani1989 let's do both, belt-and-suspenders. |
f4dc86e
to
a3e6e1e
Compare
@squeed Thanks for reviewing. Addressed your comment. |
/test |
Delegated ipam returns ipv6 address to cilium cni even if ipv6 disabled in cilium agent config. In this scenario, ipv6 node addressing is not set and its causing cilium cni to crash if delegated ipam returns ipv6 but disabled in cilium agent. Signed-off-by: Tamilmani <tamanoha@microsoft.com>
a3e6e1e
to
9726361
Compare
/test |
/test |
/ci-eks |
Delegated ipam returns ipv6 address to cilium cni even if ipv6 disabled in cilium agent config. In this scenario, ipv6 node addressing is not set and its causing cilium cni to crash if delegated ipam returns ipv6.
Requires backport to 1.14 and 1.15 versions
Please ensure your pull request adheres to the following guidelines:
description and a
Fixes: #XXX
line if the commit addresses a particularGitHub issue.
Fixes: <commit-id>
tag, thenplease add the commit author[s] as reviewer[s] to this issue.
Fixes: #31103