You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Over time, it appears that kube-router hits conditions where it will keep BGP routes that have since been withdrawn. This likely happens because route_sync.go contains its own cache of routes and at some point it isn't able to receive a BGP update for one reason or another.
Because of this problem, kube-router continues to put back bad routes to nexthops that no longer contain the service which essentially blackholes the traffic bound for that service.
What did you expect to happen?
kube-router to have an accurate route state at all times.
How can we reproduce the behavior you experienced?
This behavior is not easily reproduced and the exact cause of the issue is not yet known. It is something that involves state over time.
System Information (please complete the following information)
Kube-Router Version (kube-router --version): 2.1.3
This would allow the controller to be primarily event driven, but also retrue it's state from time to time to ensure that it doesn't get into an inconsistent state with the desired state of the BGP subsystem.
The text was updated successfully, but these errors were encountered:
What happened?
Over time, it appears that kube-router hits conditions where it will keep BGP routes that have since been withdrawn. This likely happens because route_sync.go contains its own cache of routes and at some point it isn't able to receive a BGP update for one reason or another.
Because of this problem, kube-router continues to put back bad routes to nexthops that no longer contain the service which essentially blackholes the traffic bound for that service.
What did you expect to happen?
kube-router to have an accurate route state at all times.
How can we reproduce the behavior you experienced?
This behavior is not easily reproduced and the exact cause of the issue is not yet known. It is something that involves state over time.
System Information (please complete the following information)
kube-router --version
): 2.1.3kubectl version
) : 1.28.10Logs, other output, metrics
No logs show up with this issue
Additional context
kube-router probably needs to add a consistency check that happens periodically when the routes_sync controller is running.
This would allow the controller to be primarily event driven, but also retrue it's state from time to time to ensure that it doesn't get into an inconsistent state with the desired state of the BGP subsystem.
The text was updated successfully, but these errors were encountered: