Aaron U'Ren 367aedf846 fix(bgp_policies): add empty DS set checking ...

Without this logic, it appears that sometimes GoBGP is inclined to match
unintentional routes in policy because of the MATCHSET_ANY declaration
and the way that it interacts with empty sets.

In my testing, without this logic I found that it often resulted in
various routes not being advertised correctly and not even showing up in
GoBGP itself. My current guess is that policy keeps GoBGP from importing
the route into the RIB even from the Protobuf socket connection that
kube-router establishes directly.

2023-10-07 08:52:31 -05:00

..

aws.go

feat(.golangci.yml): enable long lines linter and remediate

2021-09-11 16:20:07 -05:00

bgp_peers.go

fix(bgp_peers): adv. AfiSafi based on capabability

2023-10-07 08:52:31 -05:00

bgp_policies_test.go

test(bgp_policies_test): add local address

2023-10-07 08:52:31 -05:00

bgp_policies.go

fix(bgp_policies): add empty DS set checking

2023-10-07 08:52:31 -05:00

ecmp_vip_test.go

fix(NRC): withdraw advertised VIPs based on annotation

2023-07-17 08:20:05 -05:00

ecmp_vip.go

fix(ecmp_vip): handle ipv4 & ipv6 protocols

2023-10-07 08:52:31 -05:00

network_routes_controller_test.go

feat(NRC): make NRC dual stack

2023-10-07 08:52:31 -05:00

network_routes_controller.go

fix(NRC): ensure local addr IP is bindable early

2023-10-07 08:52:31 -05:00

pbr.go

feat(NRC): make NRC dual stack

2023-10-07 08:52:31 -05:00

pod_egress.go

feat(NRC): make NRC dual stack

2023-10-07 08:52:31 -05:00

route_sync_test.go

test(sync_routes): add unit testing

2022-03-18 15:02:02 -05:00

route_sync.go

feat(NRC): make NRC dual stack

2023-10-07 08:52:31 -05:00

utils_test.go

feat(bgp): add custom BGP import rejection policy support via node annotation

2022-03-23 09:27:38 -05:00

utils.go

fix(ecmp_vip): handle ipv4 & ipv6 protocols

2023-10-07 08:52:31 -05:00