Is there an existing issue for this?
Version
equal or higher than v1.17.0 and lower than v1.18.0
What happened?
enableNeighDiscovery isn't initialized at the time this code is called and migrateOnly is always false. As a result, the managed neigh entries are being deleted. NodeConfigurationChanged callback initializes enableNeighDiscovery but it hasn't been called when the daemon calls NodeCleanNeighbors.
This causes connection disruption when the XDP acceleration is enabled.
How can we reproduce the issue?
Restart a cilium-agent Pod.
Cilium Version
v1.17 (main branch)
Kernel Version
Linux 320 6.8.0-52-generic #53~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Wed Jan 15 19:18:46 UTC 2 x86_64 x86_64 x86_64 GNU/Linux
Kubernetes Version
v1.32.1
Regression
No response
Sysdump
No response
Relevant log output
Anything else?
No response
Cilium Users Document
Code of Conduct
Is there an existing issue for this?
Version
equal or higher than v1.17.0 and lower than v1.18.0
What happened?
enableNeighDiscovery isn't initialized at the time this code is called and
migrateOnlyis always false. As a result, the managed neigh entries are being deleted.NodeConfigurationChangedcallback initializesenableNeighDiscoverybut it hasn't been called when the daemon callsNodeCleanNeighbors.This causes connection disruption when the XDP acceleration is enabled.
How can we reproduce the issue?
Restart a cilium-agent Pod.
Cilium Version
v1.17 (main branch)
Kernel Version
Linux 320 6.8.0-52-generic #53~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Wed Jan 15 19:18:46 UTC 2 x86_64 x86_64 x86_64 GNU/Linux
Kubernetes Version
v1.32.1
Regression
No response
Sysdump
No response
Relevant log output
Anything else?
No response
Cilium Users Document
Code of Conduct