Version
0.8.0
Describe the bug.
Users can provide a list of IPs as route_server in NICo config. NICo sends these to DPUs where DPU agent renders every route server as a BGP neighbor in the routeserver peer group.
However, if any of the route server is having issues, NICo creates BgpPeeringRouteServer health alert with PreventAllocations and PreventHostStateChanges classification. If route servers are redundant and carry the same EVPN routes (which should be in production settings), the classifications would unnecessarily reduce available capacity of the site or blocking of host operations.
NICo should be smarter in handling partial availability of route servers. If there is no redundancy or no route server, then NICo should really alert/mark the machines as unhealthy. Otherwise, it would serve better with some warning or metric that operators can alert on.
Minimum reproducible example
Relevant log output
Other/Misc.
No response
Code of Conduct
Version
0.8.0
Describe the bug.
Users can provide a list of IPs as
route_serverin NICo config. NICo sends these to DPUs where DPU agent renders every route server as a BGP neighbor in the routeserver peer group.However, if any of the route server is having issues, NICo creates
BgpPeeringRouteServerhealth alert withPreventAllocationsandPreventHostStateChangesclassification. If route servers are redundant and carry the same EVPN routes (which should be in production settings), the classifications would unnecessarily reduce available capacity of the site or blocking of host operations.NICo should be smarter in handling partial availability of route servers. If there is no redundancy or no route server, then NICo should really alert/mark the machines as unhealthy. Otherwise, it would serve better with some warning or metric that operators can alert on.
Minimum reproducible example
Relevant log output
Other/Misc.
No response
Code of Conduct