Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

BGP-based implementation for Flexible IPAM #6548

Open
antoninbas opened this issue Jul 25, 2024 · 0 comments
Open

BGP-based implementation for Flexible IPAM #6548

antoninbas opened this issue Jul 25, 2024 · 0 comments
Labels
area/ipam Issues or PRs related to IP address management (IPAM). area/transit/bgp Issues or PRs related to BGP support. kind/feature Categorizes issue or PR as related to a new feature. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.

Comments

@antoninbas
Copy link
Contributor

antoninbas commented Jul 25, 2024

If we interpret "Flexible IPAM" as the ability to assign arbitrary IPs to Pods, without looking at the current implementation (which requires bridging mode), then maybe this is something that BGP can actually help achieve (when supported by the underlay) without requiring that the Node's transport interface be moved to the OVS bridge?

Note: that would be a L3 approach to Flexible IPAM, not a L2 approach using VLANs (current approach).

Originally posted by @antoninbas in #6203 (comment)

As pointed out by @tnqn in the above discussion, that would generally require that Nodes be able to learn routes from BGP peers, which was out-of-scope of our initial BGP implementation (#5948). This could also enable additional use cases, e.g. for multicluster routing.

@antoninbas antoninbas added area/ipam Issues or PRs related to IP address management (IPAM). area/transit/bgp Issues or PRs related to BGP support. kind/feature Categorizes issue or PR as related to a new feature. labels Jul 25, 2024
@antoninbas antoninbas added the lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. label Sep 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/ipam Issues or PRs related to IP address management (IPAM). area/transit/bgp Issues or PRs related to BGP support. kind/feature Categorizes issue or PR as related to a new feature. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.
Projects
None yet
Development

No branches or pull requests

1 participant