Yutaro Hayakawa
Yutaro Hayakawa
In BGP, in the case of the multi-pool IPAM, users should rely on `podIPPoolSelector` and shouldn't rely on `exportPodCIDR`. So, disabling `exportPodCIDR` is the right solution in this particular case,...
> We have no such way, besides checking the running IPAM mode. My long-term hope is that we can just remove the auto-generated pod CIDR logic (or make it opt-in)...
@bewing Yep, please file a separate issue if there's no existing one. Thanks!
I guess your server already runs some routing daemon (because your network is "fully routed"), and you're advertising default routes from your ToRs and setting a metric only to allow...
@MrFreezeex Hi, thanks for your clarification! > As the derived service is already the aggregated/conflict resolved version we need to somehow have a way to find which cluster has what...
Note - GoBGP allows to change the next-hop with Policy (https://github.com/osrg/gobgp/blob/master/docs/sources/policy.md) - Annotation vs extending CRD, which is better?
I want to avoid annotation as much as possible. I agree that `cilium.io/bgp-virtual-router.{asn}` is a quick win. However, I feel like this is a more generic problem and not specific...
~~I think [this PR](https://github.com/osrg/gobgp/pull/2803) fixed the issue which is released in [v3.26.0](https://github.com/osrg/gobgp/releases/tag/v3.26.0).~~ ~~In Cilium, we could reproduce with the version using GoBGP v3.23.0, but couldn't with the latest main using...