BGP Timer and BFD Support #7672
Replies: 1 comment
-
|
This would be a useful enhancement. Today, BGPPolicy intentionally exposes only a minimal set of BGP parameters (ASN, peer address, port, and advertisements). Configuration of BGP timers and BFD is not currently supported through the API. That said, both features are commonly required in production BGP deployments: Configurable BGP timers (hold/keepalive) would allow better interoperability with external routers and faster detection of failed peers. BFD support would significantly improve convergence times compared to relying on BGP timers alone. Adding this would likely require: Extending the BGPPolicy API with optional fields for timers and BFD Ensuring the underlying BGP implementation supports these features Careful consideration of defaults and validation to avoid impacting existing users This seems suitable for a follow-up design proposal if there is interest from the community, as it involves both API changes and controller behavior updates. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
It would be great if you could configure BGP timers and BFD in the BGPPolicy.
apiVersion: crd.antrea.io/v1alpha1
kind: BGPPolicy
metadata:
name: bgp-policy
namespace: kube-system
spec:
nodeSelector: {}
localASN: 65422
listenPort: 179
advertisements:
service:
ipTypes: [LoadBalancerIP, ExternalIP]
pod: {}
bgpPeers:
asn: 65421
port: 179
Beta Was this translation helpful? Give feedback.
All reactions