Add support for configuring the BGP control plane #118
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Rendered from template version: main (26ee71e)
simu
force-pushed
the
feat/bgp-control-plane-config
branch
3 times, most recently
from
ceeb649 to
34636b4
Compare
This will be the key used by Cilium 1.15. The component internally ensures that blocks defined in top-level key `blocks` of an IP pool definition are correctly written to `spec.cidrs` for Cilium <= 1.14. Note that the contents of top-level key `spec` are not rewritten.
simu
force-pushed
the
feat/bgp-control-plane-config
branch
from
34636b4 to
762faea
Compare
DebakelOrakel
approved these changes
Jul 9, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR introduces parameters which allow users to configure
CiliumBGPPeeringPolicyandCiliumLoadBalancerIPPoolcustom resources.Checklist
changelog.
The PR has a meaningful description that sums up the change. It will be
linked in the changelog.
bug,enhancement,documentation,change,breaking,dependencyas they show up in the changelog.