Commits on Jul 25, 2024

1. Implement the controller for API BGPPolicy …

   This commit implements the controller of API `BGPPolicy`, designed to advertise
   Service IPs, Egress IPs, and Pod IPs to BGP peers from selected Kubernetes Nodes.
   
   According to the spec of `BGPPolicy`, the Node selector is used to select Nodes
   to which a `BGPPolicy` is applied. Multiple `BGPPolicies` can be applied to the
   same Node. However, only the oldest `BGPPolicy` will be effective on a Node,
   with others serving as alternatives. The effective one may be changed in the
   following cases:
   
   - The current effective BGPPolicy is updated and not applied to the Node.
   - The current effective BGPPolicy is deleted.
   
   The BGP server instance is only created and started for the effective BGPPolicy on
   a Node. If the effective BGPPolicy is changed, the corresponding BGP server instance
   will be terminated by calling the `Stop` method, and a new BGP server instance will
   be created and started by calling the `Start` method for the new effective BGPPolicy.
   
   To create a BGP server instance, ASN, router ID, and listen port must be specified.
   The ASN and listen port are specified in the spec of the effective BGPPolicy. For router ID,
   if the Kubernetes cluster is IPv4-only or dual-stack, we use the Node's IPv4 address
   as the router ID, ensuring uniqueness. If the Kubernetes cluster is IPv6-only, where no
   Node IPv4 address is available, the router ID could be specified via the Node annotation
   `node.antrea.io/bgp-router-id`. If not present, a router ID will be generated by hashing
   the Node name and update it to the Node annotation `node.antrea.io/bgp-router-id`.
   Additionally, the stale BGP server instance will be terminated and a new BGP server
   instance should be created and started when any of ASN, routerID, or listen port changes.
   
   The information of the BGP peers is specified in the effective BGPPolicy. The unique
   identification of a BGP peer is the peer IP address and peer ASN.
   
   To reconcile the latest BGP peers:
   
   - Get the BGP peers to be added and add them by calling the `AddPeer` method of the
     BGP server instance.
   - Get the BGP peers to be deleted and delete them by calling the `RemovePeer` method
     of the BGP server instance.
   - Get the remaining BGP peers and calculate the updated BGP peers, then update them by
     calling the `UpdatePeer` method of the BGP server instance.
   
   The information of the IPs to be advertised can be calculated from the spec of the
   effective BGPPolicy. Currently, we advertise the IPs and CIDRs to all the BGP peers.
   
   To reconcile the latest IPs to all BGP peers:
   
   - If the BGP server instance is newly created and started, advertise all the IPs by
     calling the `AdvertiseRoutes` method.
   - If the BGP server instance is not newly created and started:
     - Get the IPs/CIDRs to be added and advertise them by calling the `AdvertiseRoutes` method.
     - Get the IPs/CIDRs to be removed and withdraw them by calling the `WithdrawRoutes` method.
   
   The feature is gated by the alpha `BGPPolicy` feature gate and only supported in Linux.
   
   Signed-off-by: Hongliang Liu <[email protected]>

   

   hongliangl committed Jul 25, 2024
   Configuration menu

   • View commit details
   • Copy full SHA for 3d33c51
   • Browse repository at this point

   Copy the full SHA

   3d33c51 View commit details

   Browse the repository at this point in the history