Open brunodzogovic opened 4 months ago
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle rotten
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle rotten
What would you like to be added
Add the BGP control-plane routing to the Cilium CNI. The current working solution is deprecated which involves MetalLB BGP control-plane and thus one needs to send the BGP announcements from Cilium to MetalLB. The new goBGP solution will allow this without the need for MetalLB and by using the type LoadBalancer to expose pods and services to external BGP routes.
Note that for the goBGP control-plane to work, one must disable the MetalLB control-plane.
Why is this needed
The MetalLB BGP integration with Cilium is being deprecated and for now only security updates are being pushed. It can provide a simplified way to integrate clusters running Cilium with existing BGP infrastructure and spine routers.