-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
bgpv2: Fix defaulting of BGP peer config #33392
Conversation
/test |
29aa491
to
7169d69
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good 🚀
@rastislavs Do you think we should backport it to 1.16? |
I was able to repro a crash if peerConfigRef is not set in the CRD.
It makes sense to backport it and mark it as a bug instead of an enhancement. |
Ack, will mark & backport as bug. |
Also, maybe add a release blocker for 1.16. |
/test |
Another place this fix is required : method |
7169d69
to
fe0be9e
Compare
@harsimran-pabla fixed |
/test |
Use default peer config only when PeerConfigRef is not specified. If it is specified but not existing, skip the peer configuration instead of using the default values. Signed-off-by: Rastislav Szabo <[email protected]>
fe0be9e
to
2a19c24
Compare
/test |
Fixes a crash when PeerConfigRef is not specified & uses the default peer config only when PeerConfigRef is not specified in
CiliumBGPClusterConfig
/CiliumBGPNodeConfig
. If it is specified but not existing, skips the peer configuration instead of using the default values.This avoids unnecessary session reset during session setup when both
CiliumBGPClusterConfig
andCiliumBGPPeerConfig
are configured in a single batch, but PeerConfig does not exist yet at the time of processing the ClusterConfig / NodeConfig.It also makes it more obvious for the users if they misspell the peer config name in the
PeerConfigRef
(peer will not be configured instead of configuring it with the default config).